[MGNLUI-5281] Consider explicit mute API for the ViewContexts in UI Created: 12/Jul/19 Updated: 10/Mar/21 Resolved: 10/Mar/21 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Aleksandr Pchelintcev | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Date of First Response: | |
| Epic Link: | UI framework: basic features |
| Sprint: | later |
| Description |
|
It appears to be quite common case that two context depend on each other. E.g. value context of a sub-app depends on the location ctx and vice versa. This might lead to the situation when updating one of such ctx's will lead to an update to another and eventually cause the endless loop. This forces us to use this or that so far ad hoc workaround as a circuit-breaker. Question is - can we introduce a simple API which devs could use as workaround, not having to fallback to custom fixes in each and every place? (see e.g. current impl of GridView) |
| Comments |
| Comment by Roman Kovařík [ 10/Mar/21 ] |
|
Doesn't seem critical anymore. Feel free to reopen.
|