[MAGNOLIA-6086] Registry/RegistryFacade API - propose functionality and implementation improvements Created: 18/Feb/15  Updated: 09/May/16  Resolved: 03/Sep/15

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

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

Issue Links:
dependency
depends upon MAGNOLIA-6027 IoC: Support multi-binding 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)
Date of First Response:
Epic Link: Definitions app
Sprint: Sprint (Basel) 8
Story Points: 5

 Description   
  • Verify naming
  • Possibly allow for registering the DefinitionTypes/SourceTypes
  • Introduce Guice multibinding or allow for registering registries individually/explicitly (void registerRegistry(Registry registry)).
  • Decide whether query API (by module/by type) should have methods returning grouped maps (Map<source, Collection<DefProv> groupBySource()).
  • Implement grouping by source (RegistryFacadeImpl#bySource).


 Comments   
Comment by Jan Haderka [ 21/Aug/15 ]

Aim is to specify and get approval for necessary changes before proceeding with implementation.

Comment by Aleksandr Pchelintcev [ 03/Sep/15 ]

The proposals for improvements are listed on the linked page.

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