feat: upgrade to Angular 19 #11
Draft
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
jxhnx
force-pushed
the
feat/upgrade-to-angular-19
branch
from
13c57cb to
d21e985
Compare
FabianScheidt
force-pushed
the
feat/upgrade-to-angular-19
branch
from
d21e985 to
3d44c39
Compare
|
@jxhnx the dependency updates look good to me. Following the suggestion of the linter (and out of curiosity), I have updated the components to be standalone. Can you double-check if everything is still working as expected? |
FabianScheidt
force-pushed
the
feat/upgrade-to-angular-19
branch
from
08bf6a7 to
8ddf984
Compare
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.
Follow up of #10 ; needs some adjustments regarding eslint:
Components, Directives and Pipes should not opt out of standalone @angular-eslint/prefer-standalone