[MGNLUI-4281] When resolving app names for IoC annotations from the XML components ids - use the longest matching app name Created: 28/Aug/17  Updated: 04/Sep/17  Resolved: 31/Aug/17

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 5.5.5
Fix Version/s: 5.5.7, 5.6

Type: Bug Priority: Critical
Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
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
Sprint: Basel 111
Story Points: 3

 Description   

There might be several apps in the system that might have very similar name, e.g. articles, articles-custom, articlesOld and so on. Currently when module descriptor contains a component mapping section with i.d. equal to e.g. <id>app-articlesOld-mysubapp, the IoC mechanism may screw things up because it might think that the components from this section are bound to the app articles because of the too permissive pattern matching.

Solution would be to choose the app whose name is longest among the matching ones (instead of picking the first one matching).


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