...
......
primaryButton:{
componentPath:"Button",
props:{
variant:"contained",
color:"primary"
}
}
......
Version 1.0 feature
1. Basic atoms.
2. Basic molecules.
3. Basic containers.
4. Inbuild localization support.
5. Role based components.
6. Dynamically create objects using json path.
7. Full screen configuraion.
8. Breaking up the configuration into multiple js.
9. Support multiple frameworks.
10.Inbuilt util functions.
11.Inbuilt component and screen interfaces.
Version 2.0 feature
1. Auto submit functionality with configuration.
2. Moving configuration to github based on tenant.
3. Enhancments of atoms, molecules and container.
4. Userfriendly configurations.
5. Removing unused components.
6. Enhancment of multiitem containers.
........................................................................................................
Rules to write specs for rendering pages/components:
- specs can be written inside any folder on this path "\src\ui-config\screens\specs\".
- below are the usages in specs:
ui-framework options to write in the specs:
| ui-framework | within module components (local) | framework components |
|---|---|---|
| containers | custom-container-local | custom-container |
| molecules | custom-molecules-local | custom-molecules |
| atoms | custom-atoms-local | custom-atoms |
- If Ui-framework is using local components(eg: atoms, molecules, containers), it's mandatory to mention the module name (eg: moduleName: "egov-ui-tradelicence")
File imports to handle both indivisual module app and citizen/employee app.
- each module has a common config file to maintain all the imports in a common way to support both running the app individually and through citizen and employee.
- common config (path: "\src\ui-config\commonConfig") two configs named remote-component-paths and remote-config-paths to store the paths with respect to the modules.