[CONTEDIT-109] Improve and centralize handling of available blocks Created: 10/May/17  Updated: 02/Jun/21  Resolved: 02/Jun/21

Status: Closed
Project: Content Editor
Component/s: None
Affects Version/s: 1.0.4
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Philip Mundt Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to CONTEDIT-107 Inline block picker doesn't order AND... 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: Content editor next
Story Points: 5

 Description   

At the moment we handle available (unavailable) blocks in various places:

  • info.magnolia.editor.content.blockpicker.BlockRegistryContentConnector#getBlockDefinitions
  • info.magnolia.editor.content.editor.DefaultContentEditor#getBlockDefinition
  • info.magnolia.editor.app.ContentEditorSubApp#ContentEditorSubApp

This needs to be improved.


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