feat: Add support for legagy Angular v15 theming. #149
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
1 task
JeffGreiner-eaton
added
the
brightlayer-ui
JeanMeche
force-pushed
the
feature/ng15
branch
from
9417404
to
503c54e
Compare
|
Awesome! Looking forward to this being merge |
JeanMeche
force-pushed
the
feature/ng15
branch
from
503c54e
to
ecd74e1
Compare
JeanMeche
force-pushed
the
feature/ng15
branch
from
ecd74e1
to
f935636
Compare
daileytj
approved these changes
Feb 27, 2023
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.
Since the move to v15, Angular supports 2 type of components :
The commit adds the support of theming for Angular legacy components only.
Maybe it should be discussed if this lib should also directly provide support for non-legacy theming.
Fixes: #143