UI 2.0: /api/ui/ Endpoint for Detail View Layout

[bryanculver]

For the 2.0 UI, data will be retrieved from the existing REST API endpoints. However, the UI will need to have some way to determine where the attributes should live in a section on the view.

For example here:

The UI will need to know the grouping, ordering, and potentially tab location for what is returned from the REST API response.

This should be viewed as the 80% case (models without heavy view customization) as anything sufficiently more nuanced will need to register its own view.

Models that don't define their own, should still get a response from this endpoint that is fairly generic (all models fields under one section, things like tags can be broken out). Things like Status, Created, Last Updated appears in the title bar and are special cases. API response should inform you of those.

TODO

• Design and define the convention, and provide Device as an example that overrides the default

Follow-on:

• Update views to take advantage of this endpoint exists (currently would be blocked by the base views and presentation not existing at the moment)
• Create backlog for defining overloaded model view definitions
• Need to address/be able to extend this endpoint for the related objects on detail views (Images, Services, etc from above)

[bryanculver]

Implemented with #3816