Resource introspection (e.g. be more DRY!)
Registered by
Gabriel Hurley
An ENORMOUS amount of the code in the dashboards right now is boilerplate CRUD which can all be abstracted into a few lines of code if we simply had proper resource introspection for the resources returned by the clients. Things like names, tables, basic actions, etc. can all be done for 90% of cases with a default sane set of generators.
There are HUGE wins to be had here, and it will make adding new management interfaces in the future nearly trivial.
Blueprint information
- Status:
- Complete
- Approver:
- Gabriel Hurley
- Priority:
- Medium
- Drafter:
- Gabriel Hurley
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Matthias Runge
Related branches
Related bugs
Sprints
Whiteboard
This blueprint has no urgency, it is merely an extremely "nice-to-have". It's also best done towards the beginning of a release cycle as it will incur very large changes.
As such I'm going to knock it out of Grizzly entirely and return to it at the beginning of H.
(?)
