[MGNLUI-5111] Prevent ViewContextParameterResolver from resolving IoC-annotated c-tor params Created: 26/Mar/19  Updated: 16/May/19  Resolved: 15/May/19

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: None
Fix Version/s: 6.1

Type: Bug Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 1.55h
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLUI-5085 Minor glitches in tasks/notifications Closed
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Epic Link: UI framework: basic features
Sprint: Foundation 7, Foundation 8, Foundation 9, Foundation 10
Story Points: 3

 Description   

If the parameter is annotated with a Guice binding annotation (or javax.inject.Named which is of the same sort - do not attempt to resolve it and let Guice param resolver handle the case.

Most obvious case is the EventBus which is present in pretty much every view's store and would be resolved by this parameter, but it conflicts with our Named annotation based approach of "scoping" the event buses.


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