Module extensibility
Angular applications are modular and you can modify and extend the components of these modules if the business use case demands it.
About this task
Angular applications are modular and Angular has its own modularity system called
NgModules. NgModules are containers for a cohesive block of code
dedicated to an application domain, a workflow, or a closely related set of capabilities. They can
contain components, service providers, and other code files whose scope is defined by the containing
NgModule.
All the Business Flows in Sterling Store
Engagement are organized as
NgModules.
If the business use case demands that you have to modify most of the components belonging to a
module, then it is better to own the complete module. This ensures a seamless upgrade.
CAUTION: It is not recommended to own the module completely.
Procedure
To own the complete module, copy all the folders and files belonging to a module in
SCREEN_EXTENSIONS_HOME/features.
For example, if you want to
customize most of the components in
BackroomPickModule, namely
PickOrderListPageComponent, PickOrderPageComponent,
PickSummaryPageComponent, and modals as well, it is recommended that you copy all
the contents of src/features/backroom-pick to
SCREEN_EXTENSIONS_HOME/features/backroom-pick/.