PrimeFlex 2 to Tailwind Migration #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 5 commits
December 12, 2024 11:18
…meFlex 3 before running the Tailwind conversion and enhance PrimeFlex to Tailwind translation with new options
…in Angular bindings" This reverts commit d5f7dfa.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm supporting the migration of several old Angular apps using PrimeNG that are still using PrimeFlex 2.x and will be being updated to PrimeNG 18 with Tailwind. I haven't done extensive testing, but haven't noticed any big issues with using this on an Angular project other than the cases I covered with the updated regex and ignored directories.