[MGNLUI-4832] Node-less I18NAuthoringSupport API modifications not compatible with MultiSite case Created: 28/Nov/18  Updated: 16/Apr/19  Resolved: 16/Apr/19

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

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

Issue Links:
supersession
supersedes MGNLUI-4508 Come up with sensible package and art... 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

 Description   

Multisite impl of I18NAuthoringSupport unconditionally requires some node to be passed as a reference to determine the related website node, so that locales relevant to it are resolved.

However, in case of Vaadin 8 based UI framework modifications, components are a) JCR-agnostic and b) data binding is separated from UI, so it is hard to get an instance of a Node that e.g. a form operates on. For that purpose we introduced API version which take no arguments. For default case it works okay - there's only one website and everything is resolved fine. In multisite case, however, it breaks miserably with NPE''s.


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