[MAGNOLIA-6087] Review/Improve Registry API Created: 18/Feb/15  Updated: 22/Dec/16  Resolved: 22/Dec/16

Status: Closed
Project: Magnolia
Component/s: configuration
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: Registry & Resources API wishlist
Story Points: 8

 Description   
  • Provide methods to unregister definitions.
  • Consider separating read/write operations.
  • Consider integration with i18n.
  • Consider possibility to register non-converted objects in the form of the map.
  • getProvider method should be throwing a NoSuchDefinitionException


 Comments   
Comment by Mikaël Geljić [ 22/Dec/16 ]

This ticket belongs to a series of improvements to the 5.4 registry & resources APIs—which hasn't caught sufficient traction or rationale ever since 5.4 was released last year.

Do reopen should this become a topic again.

Generated at Mon Feb 12 04:11:11 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.