Version 0.2 made an important business component separate into a separate class library called @delon. The main benefits of this approach are to address a number of core issues:
- Ng-alain topic upgrade redundancy problem
- Business components are more reusable (not limited to NG-Alain scaffolding) and easy to maintain
- Simplify scaffolding entry costs
Currently @delon contains three subclass libraries:
@delon/theme
- Ng-alain theme system
- Several data rendering pipes
- Several common Web services (for example: page titles, scrollbar operations, network requests, etc.)
@delon/ ABC (Angular Business Componets)
- All components are based on the Antd Design style
- Each component can be imported separately
- Based on G2, the chart type is commonly used in services
- Add count-down to the existing shared/ Components
- Add several form validators (e.g. mobile phone number, ID card)
@delon/acl
- Role-based permission control
The Ng-Alain scaffolding is left with a very simple project, which builds the product further up using the @delon class library.
The @delon library itself has only one principle based on Ant Design, and since it is not actually limited to ng-Alain scaffolding, it works well for Angular projects that comply with Ant Design.
Of course, good open source documentation is important, and from 0.2 all documentation will not be in the Ng-Alain scaffolding, but in the Ng-alain.com site.
In the follow-up work, @delon/ Auth will be added to quickly solve the front-end authentication and Token management problems in Mid-platform.