
Research
/Security News
Critical Vulnerability in NestJS Devtools: Localhost RCE via Sandbox Escape
A flawed sandbox in @nestjs/devtools-integration lets attackers run code on your machine via CSRF, leading to full Remote Code Execution (RCE).
@salesforce-ux/c360-button
Advanced tools
The button represent an control that should invoke an action
@salesforce-ux/c360-button
The button represent an control that should invoke an action
Let's start by installing c360-button as a dependency of your project with npm.
npm i @salesforce-ux/c360-button
After installation, all the distributables for the c360-button
are found under /node_modules/@salesforce-ux/c360-button/dist/
folder.
File Name | Description |
---|---|
button.css | The CSS file specific to c360-button only. It doesnot include the styles for it's parent sds-button . c360-button extends from sds-button |
button.compiled.css | The Compiled CSS file for c360-button . This file includes styles for both c360-button and its parent sds-button . This file is useful for LWC applications.(see below →) |
button.js | The bundled JS file for c360-button component. This file is useful for Non LWC applications.(see below →) |
c360-button
IntegrationFor the sake of understanding, we will categorize the development environment into LWC and Non LWC application.
This Guide will cover the integration approach for these two types of application.
Lightning Web Component(LWC)
ApplicationDependency Inclusion
c360-styling-hooks
is a styling dependency for c360-button
. Hence, this needs to be embedded into your web app in order to make the c360-button
render properly.
/* myComponent.css */
@import "@salesforce-ux/c360-styling-hooks/dist/hooks.custom-props.css";
There are also other ways c360-styling-hooks
can be embedded. Please checkout the c360-styling-hooks
Integration Guide to learn more.
Component CSS Import
/* myComponent.css */
@import "@salesforce-ux/c360-styling-hooks/dist/hooks.custom-props.css";
@import "@salesforce-ux/c360-button/dist/button.compiled.css";
HTML Decoration
After that,the HTML of your LWC component template needs to be decorated to have all the named part attributes as per the component's specification. Below is a reference to the component's structure.
<c360-button>
<button part="button">
<slot name="start" part="start"></slot>
Label
<slot name="end" part="end"></slot>
</button>
</c360-button>
Non LWC
ApplicationDependency Inclusion Read the section above
Component Import
/* myComponent.js */
import C360Button from "@salesforce-ux/c360-button/dist/button";
Component Registration
/* myComponent.js */
customElements.define('c360-button', C360Button);
Below is one approach to integrate your c360-button
component.
/* myComponent.js */
import "@salesforce-ux/c360-styling-hooks/dist/hooks.custom-props.css";
import C360Button from "@salesforce-ux/c360-button/dist/button";
window.customElements.define('c360-button', c360Button);
<c360-button variant="primary" size="small">
Click
</c360-button>
To see more examples with interactive demo, please visit c360 Subsytem
's Storybook Environment
FAQs
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
/Security News
A flawed sandbox in @nestjs/devtools-integration lets attackers run code on your machine via CSRF, leading to full Remote Code Execution (RCE).
Product
Customize license detection with Socket’s new license overlays: gain control, reduce noise, and handle edge cases with precision.
Product
Socket now supports Rust and Cargo, offering package search for all users and experimental SBOM generation for enterprise projects.