[MGNLFE-32] Unify Angular library to handle metadata like React library Created: 19/Mar/20 Updated: 03/Jun/20 Resolved: 23/Apr/20 |
|
| Status: | Closed |
| Project: | Magnolia Frontend Helpers |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0.1 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Christopher Zimmermann | Assignee: | Robert Šiška |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 0.5d | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Documentation update required: |
Yes
|
||||||||
| Date of First Response: | |||||||||
| Epic Link: | SPA Editor | ||||||||
| Sprint: | 6.2.1 Ramp-up 22 | ||||||||
| Story Points: | 5 | ||||||||
| Description |
|
React library has a nice feature which puts all jcr*, mgnl*, @* prefixed properties to a 'metadata' property after loading the content from the REST endpoint. This makes the content much cleaner to work with and improves the developer experience. This is now a significant difference between our React and Angular libraries. Documentation and education will be simpler and easier if we update the angular library to also have this behaviour. |
| Comments |
| Comment by Christopher Zimmermann [ 09/Apr/20 ] |
|
What would this be: " just make small changes to pass user define properties into developers' components."? As I recall, currently everything is passed in on the 'content' property. How would that change? |
| Comment by Mikaël Geljić [ 10/Apr/20 ] |
|
Top-level content/properties still want to be strongly typed and declared explicitly, don't they? All good, thanks for the summary! |