pa-lem
commented
11 months ago If the frontend is splitting the schema in multiple components in the schema view, each component can handle only a part of the schema
So maybe having a parameter in the schema endpoint to query only part of the schema would help the frontend to not query the whole schema on each update, and to be able to update just some parts of it
Having something like /api/schema/{id}may be useful to get only the information for a specific node (object, attribute, relationship, etc), so when updating a part of the schema after an update, only that current part will be fetched again
Component
Frontend UI, API Server / GraphQL
Describe the Feature Request
The flexibility offered by Infrahub to modify the schema on the fly is one of its main differentiators.
Today the modification of the schema must be done via the /api/schema/load endpoint and it requires a schema file in YAML or JSON format. The end goal is that a user should be able to modify any part of the schema directly in the frontend.
A new set of GraphQL mutations will be required to expose the main operations that we need to support. Below is a list of the main mutations that we need to add, ordered by level of complexity:
In the Frontend, the manipulation of the schema should be available both in a dedicated section reserved for the schema management but, whenever possible, directly within a create or update forms.
Describe the Use Case
The end goal is that a user should be able to modify any part of the schema directly in the frontend.
Additional Information
Some operations won't be available at first until we have a proper support for these changes in the schema migrations.