[MGNLFE-512] Upgrade angular-editor to use Angular 16 Created: 19/Jun/23  Updated: 14/Dec/23  Resolved: 07/Dec/23

Status: Closed
Project: Magnolia Frontend Helpers
Component/s: None
Affects Version/s: None
Fix Version/s: 1.6.0-angular

Type: Story Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Phong Le Quoc
Resolution: Done Votes: 0
Labels: None
Σ Remaining Estimate: 0d Remaining Estimate: 0d
Σ Time Spent: 12d 2.25h Time Spent: 12d 2.25h
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
dependency
relation
is related to MGNLFE-591 Support "standalone components" in An... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLFE-725 Implement Sub-task Closed Phong Le Quoc  
MGNLFE-726 Review Sub-task Completed Oanh Thai Hoang  
MGNLFE-727 PiQA Sub-task Closed Anh Vu  
MGNLFE-728 QA Sub-task Completed Chuong Doan Huy  
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:
Epic Link: SPA Library Updates
Sprint: DevX 52
Story Points: 3
Team: DeveloperX
Work Started:

 Description   

Angular 16 introduces big changes - especially around SSR.

We should start to investigate this now and before our scheduled introduction date because it is likely to be a popular request and topic.

We should do a PoC and release a public beta so that customers and prospects can try it.

Our library should take advantage of the new features where relevant.

Some things customers may be interested in:

  • ngcc view engine dropped with Angular 16. Ivy is the successor.
  • Signals. Better state management. Don't want to use zone.js
  • Faster - performance optimized.
  • Better SSR - Improved rehydration

 



 Comments   
Comment by Phong Le Quoc [ 08/Aug/23 ]

1. For SSR:
Firstly, SSR improvement is in Preview mode only. Secondly, the new feature works without any code changes, which means we don't need to do anything except upgrade to the new version. Thirdly, there are nothing changes in the editor, only SPA if needed.

2. For signals, also in Preview mode.

The only thing we can improve now in our editor is converting it to the standalone way (support two ways for SPA) - MGNLFE-591. However, we can do this on Angular 14 (standalone mode is in Preview mode in Angular 14 and official in Angular 15).

In summary, we just need to change a few configs to upgrade the Angular editor when upgrading to the new Angular versions. In addition, most of the changes will happen on SPA if any.

Note:  We don't bundle Angular with our editor, so our editor can work on either Angular 14 or 15, or 16 which is bundled with SPA.

References:

https://angular.io/guide/update-to-version-16

https://blog.angular.io/angular-v16-is-here-4d7a28ec680d

 

Comment by Phong Le Quoc [ 16/Nov/23 ]

Angular 17 has been released.

https://blog.angular.io/introducing-angular-v17-4d7033312e4b

https://github.com/angular/angular/releases/tag/17.0.3

 

Comment by Jaroslav Simak [ 27/Nov/23 ]

Let's go with 16 for now, cc mmichlova

Comment by Phong Le Quoc [ 29/Nov/23 ]

czimmermann

  1. where should we push code? master or release/1.6? or?
  2. what/when should we release?

 

Note:

  • release/1.6: contains code to support nextjs-app-router - 1.6.0-experimental.6
Comment by Christopher Zimmermann [ 29/Nov/23 ]

Lets do 1.6 

Generated at Mon Feb 12 05:48:09 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.