-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maintenance and Support for Angular versions #54
Comments
The first issue: No Secondary Entry Point for Components/DirectivesAs stated from ng-packager
For library developers, secondary entry points are configured by adding a ng-package.json file in subdirectories of the main package.json file's folder! BeforeAfterand the library consumer will use it like this import { SanitizeHtmlPipe } from 'flowbite-angular/pipes' and maybe we can make it better be adding each components independently inside the src folder without need to group them (components, services, driectives) and so on. import { Button } from 'flowbite-angular/button' |
@tomavic Hey We know we have plenty of work on this side. Secondary entry points are a good way to provide developers a good experience. import { ButtonComponent } from 'flowbite-angular/components/button' In that way we will have an entry point for directive, another for component, and an entry point for each component/directive inside (as angular-material) For now I think it's better to move this issue inside a discussion and close this issue, I'll let you create one. |
Hi @MGREMY Thanks ;) |
Hey @tomavic |
(also I'm moving this into a discussion at this link) |
The question is How far can you support Angular versions?
However, After checking discord and Figma I can see there are lots of work pending. This Answer to this will narrow the amount of work needed.
In addition to the work pending such as adding components, accessibility and so on, there are developer-experience-related enhancements and refactors needed.
From my side I will try to list them here, Please feel free to add yours too.
The text was updated successfully, but these errors were encountered: