Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
@ui5/webcomponents-icons-business-suite
Advanced tools
UI5 Web Components: SAP Fiori Tools icon set
Provides assets for the rich business-suite
icon collection.
Icon asset | Module import |
---|---|
All icons (~73KB zipped) | import "@ui5/webcomponents-icons-business-suite/dist/AllIcons.js"; |
1x2 grid layout icon | import "@ui5/webcomponents-icons-business-suite/dist/1x2-grid-layout.js"; |
2x1 grid layout icon | import "@ui5/webcomponents-icons-business-suite/dist/2x1-grid-layout.js"; |
... | ... |
Year icon | import "@ui5/webcomponents-icons-business-suite/dist/year.js"; |
Note: The @ui5/webcomponents-icons-business-suite
package does not provide any web components per se, but rather icon assets,
usable by other web components such as ui5-icon
. You could import all icons, but it's recommended to import
just the ones that your app will actually use.
Since this is a non-default icon collection, all names have to be prefixed with the collection name and a /
separator when used by web components.
Example usage with <ui5-icon>
web component:
<ui5-icon name="business-suite/1x2-grid-layout"></ui5-icon>
The package provides two versions of each icon (SAP Business Suite Icons v1 and SAP Business Suite Icons v2). If you don't specify the versioned collection name, like in the example above:
<ui5-icon name="business-suite/1x2-grid-layout"></ui5-icon>
the framework will detect the current theme and render the corresponding icon - from SAP Icons Business suite V2
(collection name business-suite-v2
) for SAP Horizon theme family (sap_horizon, sap_horizon_dark, etc.), and from SAP Icons Business suite V1
(collection name business-suite-v1
) for all the rest (sap_fiori_3, sap_fiori_3_dark, etc.).
business-suite-v1
and business-suite-v2
In case you want to always display the SAP Icons Business suite V1
icons in all themes, you can set it explicitly via the business-suite-v1
collection name:
<ui5-icon name="business-suite-v1/answered"></ui5-icon>
The same applies if you want to always display the SAP Icons Business suite V2
icons. You can set it explicitly via the business-suite-v2
collection name:
<ui5-icon name="business-suite-v2/answered"></ui5-icon>
For a full list of the icons in the business-suite
collection, click here.
We welcome all comments, suggestions, questions, and bug reports. Please follow our Support Guidelines on how to report an issue, or chat with us in the #webcomponents
channel of the OpenUI5 Community Slack.
Please check our Contribution Guidelines.
Copyright (c) 2019 SAP SE or an SAP affiliate company. All rights reserved. This file is licensed under the Apache Software License, Version 2.0 except as noted otherwise in the LICENSE file.
2.5.0-rc.3 (2024-12-05)
FAQs
UI5 Web Components: SAP Fiori Tools icon set
The npm package @ui5/webcomponents-icons-business-suite receives a total of 32,921 weekly downloads. As such, @ui5/webcomponents-icons-business-suite popularity was classified as popular.
We found that @ui5/webcomponents-icons-business-suite demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 5 open source maintainers collaborating on the project.
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.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.