Details
-
Story
-
Status: Closed (View Workflow)
-
TBD
-
Resolution: Done
-
-
ERM Sprint 112, ERM Sprint 113
-
Bienenvolk
Description
Description:
- Capture and store frontend application that can be referenced by widget definitions and efficiently reused for widget outputs and interactions
Breakdown:
- We need to figure out which information we wish to store about frontend operations.
- Initially I would like to include:
-
- A description of all icons - do we need to constrain ourselves to stripes bundle or allow for external icons to be described as well?
- Descriptions of frontend SAS(Q) filter patterns work, possibly some kind of template?
- Similarly to the above, lists of resources managed by the entry and templated paths to those.
- Any information about plugins? - Do these have a separate registry entry?
- Should these be kept up to date by the stripes bundle itself, what does that interaction look like?
Development Tasks:
- Define registry domain structure
- Populate with agreements and licenses frontend data
- Consume registry data in dashboard Simple Search widget. Test with
- Link to object resource
- Link to filtered Search and Sort Query