![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
@pega/custom-ui-components
Advanced tools
This document captures the basic steps of initializing Pega react project and cli commands to create, publish, and list custom components to constellation.
Make sure PRPC Infinity server is available for use.
node version: 12 and above
npm version: 6 and above
If you are not on ssl (https) then make sure to uncheck “Require TLS/SSL for REST services in this package” option from service packages
dev and uiservice
$ npx @pega/custom-ui-components init
This will prompt for setting up the project with necessary details/fields
$ cd custom-ui-components
$ npm run storybook
Run command
$ npm run custom-component create CRMNumberField
OR
$ npm run custom-component create
Enter component name: Component name to be created eq., CRMNumberField
It will create a src/components folder and initializes necessary files required to build the component. Below are files
├── src
├── components
├── index.js
├── demo.stories.js
├── config.json
index.js -> Actual component rendering logic here
demo.stories.js -> Demo to see in the storybook
config.json -> Mapping of properties for auto generated property panel configuration
NOTE: Define type under config.json to Widget or Field, if we define type as Widget then component will be visible under Widgets across authoring and you will be able to author this component in landing pages as well.
Start storybook to see the demo
$ npm run storybook
Do modify the source to build your own component. You can install and import third-party libs if required for your component.
Once the changes for components are finalised, publish it to Infinity so that it can be discoverable in authoring (design palette).
$ npm run custom-component publish
options:
You can pre-configure the above options in pega.tasks.config.json for these values.
{
"components-server-config": {
"server": "http://localhost:1080/prweb",
"user": "user0",
"password": "pwd"
}
}
Once publish is successful, we can now use the newly published component in view authoring from App Studio.
Re-save ConstellationSvcURL DSS setting (in infinity) to sync components to constellation service.
NOTE:
FAQs
Utility for building custom UI components
The npm package @pega/custom-ui-components receives a total of 8 weekly downloads. As such, @pega/custom-ui-components popularity was classified as not popular.
We found that @pega/custom-ui-components demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 3 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
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.