[MAGNOLIA-6789] Optimize info.magnolia.config.registry.DefinitionQuery and its implementation and usage in registries Created: 28/Sep/16  Updated: 21/Nov/16  Resolved: 17/Nov/16

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

Type: Improvement Priority: Neutral
Reporter: Philip Mundt Assignee: Philip Mundt
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MAGNOLIA-6084 Allow for partial name search with De... Closed
is causing MAGNOLIA-6085 Allow for looking definitions up by s... 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:
Sprint: Basel 70
Story Points: 0.5

 Description   
  • Are there better patterns to pass in existing queries (create immutable query from an existing one)?
  • Is removal of methods on registries compat.?
  • ...

Side note:

  • Check possible binary compatibility issues due to removal of methods / extraction of classes


 Comments   
Comment by Jan Haderka [ 29/Sep/16 ]

Timeboxed to 1 day.

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