Extract Core Functionality from theme-shared Package to core-ui

[AhmadAlMunajjed]

Hi everyone,

Problem Statement

The theme-shared package in the ABP Framework contains some core functionality that doesn't depend on any external packages other than Angular core and ABP core. This creates unnecessary dependencies for projects that use a different UI component set.

Proposal

Extract functionality that does not depend on any external package (other than Angular core and ABP core) from the theme-shared package. This would allow developers to use these core features without installing the entire theme-shared dependency.

Examples of components that could be extracted:

• document-dir.handler
• ellipsis.directive

Benefits

1. Improved modularity: Developers can use core functionality without importing unnecessary UI components.
2. Reduced bundle size: Projects using different UI frameworks can avoid including unused code.
3. Better flexibility: Easier integration with various UI component libraries.

Use Case

In my project, I use a different set of UI components:

• fortawesome
• ng-bootstrap
• @popperjs/core
• @swimlane/ngx-datatable
• bootstrap

Being able to use core ABP functionality without the theme-shared package would streamline my development process and reduce potential conflicts.

Proposed Solution

1. Create a new package (e.g., @abp/ng.core-ui) for these extracted components.
2. Move the identified components to this new package.
3. Update the theme-shared package to import from this new package if needed.
4. Update documentation to reflect these changes.

Questions

1. Are there any potential breaking changes this might introduce?
2. What other components or directives could be candidates for this extraction?
3. Are you guys open for PRs for such a feature request or it could be implemented internally in your team?