[MGNLUI-4779] Content Types module is not effectively optional Created: 09/Nov/18  Updated: 19/Nov/18  Resolved: 14/Nov/18

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

Type: Bug Priority: Neutral
Reporter: Hieu Nguyen Duc Assignee: Mikaël Geljić
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 3h
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Sprint: Saigon 158
Story Points: 0.5

 Description   

This currently fails CE builds/UI tests.

Content-types module is not yet "effectively optional" in the UI—despite the module dependency being provider, resp. optional.

Namely, ContentTypeRegistry is injected into UiFrameworkModule. A Provider injection should cure it—then we register the custom YAML multi-construct conditionally.

 


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