Skip to content
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

Refactor Friday - Update to Angular 11 #385

Closed
Brend-Smits opened this issue Dec 7, 2020 · 3 comments · Fixed by #551
Closed

Refactor Friday - Update to Angular 11 #385

Brend-Smits opened this issue Dec 7, 2020 · 3 comments · Fixed by #551
Labels
Refactor Friday This label is used to mark an issue for a planned refactor

Comments

@Brend-Smits
Copy link
Member

Is your feature request related to a problem? Please describe.
We're currently still using outdated Angular 9...

Describe the solution you'd like
Upgrade to Angular 10 and make use of some nice optimizations that might help with things like SEO

Additional context
https://www.angularminds.com/blog/article/comparison-between-angular-9-vs-angular-10.html

@Brend-Smits Brend-Smits added the Refactor Friday This label is used to mark an issue for a planned refactor label Dec 7, 2020
@rubenb994 rubenb994 changed the title Refactor Friday - Update to Angular 10 Refactor Friday - Update to Angular 11 Dec 11, 2020
@rubenb994
Copy link
Contributor

Lets update update to v11 instead of v10

@Brend-Smits
Copy link
Member Author

Ah, right... thanks, @rubenb994!

@DamienKusters DamienKusters self-assigned this Feb 25, 2021
@DamienKusters DamienKusters removed their assignment Mar 9, 2021
@waltersajtos
Copy link
Member

@RubenFricke I can pick this up but I think it's best to do this when no one is working on any branch on the front-end. I think we can implement it at the same time as #450

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Refactor Friday This label is used to mark an issue for a planned refactor
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants