-
Notifications
You must be signed in to change notification settings - Fork 1.8k
feat(angular): update to Angular 20 #1828
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
Conversation
The latest updates on your projects. Learn more about Vercel for GitHub.
|
public user: UserService, | ||
public config: Config | ||
) { | ||
constructor() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should be using ngOnInit
so we can completely move away from constructor
(since Angular prefers inject
) but it throws a warning regarding the icons not loading in. We should look into this more since the icons did load fine so the warning is being thrown too soon.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can move most things to ngOnInit I believe, but not icon registration. There's no Angular lifecycle hook that renders soon enough for the template to know that the icons exist, so I'll keep icon registration in constructors, unfortunately.
It may be worth looking into ionicons to see if we can defer that check, but probably not as part of this upgrade.
…ndencies in the package-lock, and fixing tests
…destroy, making image in support align with other ionic images to prevent it from complaining about its resolution, updating typescript to be a bit more modern
width="200" | ||
height="200" | ||
priority | ||
/> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This image styling was conflicting with its CSS and causing a ratio conflict. In this change, I tried to make it act like the Ionic logos in its neighboring pages.
Issue URL: internal
What is the current behavior?
The app runs on Angular 19.
What is the new behavior?
Does this introduce a breaking change?
Other information
N/A