Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create an API which allows to update schema partially #391

Open
arihantjain8118 opened this issue Apr 11, 2023 · 2 comments · May be fixed by #1057
Open

Create an API which allows to update schema partially #391

arihantjain8118 opened this issue Apr 11, 2023 · 2 comments · May be fixed by #1057
Assignees
Labels
area/schema Issues related with modeling and schema. area/services Issues related with api services and functionalities. feature request New feature or request

Comments

@arihantjain8118
Copy link

arihantjain8118 commented Apr 11, 2023

Is your feature request related to a problem? Please describe.
I have less frequent but essential schema changes on my project for which i have to change full schema and for that too I have to handle it soley from BE.

Describe the solution you'd like
An API which allows us to update the partial schema (relation and action ) would work

@EgeAytin EgeAytin added area/services Issues related with api services and functionalities. area/schema Issues related with modeling and schema. feature request New feature or request labels Apr 11, 2023
@liuhx1027
Copy link

we would like to have this feature as well. here is our use case

  • we have multiple teams developing new api endpoints on daily basis
  • each new endpoint may require a new action defined in the schema
  • we would like to enable each team to add new actions by themselves while maintaining the entity and relation centrally

with that being said, it would be great if we can update the schema partially - to be specific, add new actions on existing entities without having to upload the whole schema

@tolgaOzen
Copy link
Member

Hello @liuhx1027 and @arihantjain8118, a feature like this can be implemented. It's validated by merging with the previous version before any partial entity change, then published as a new version with the merged model. Because it is versioned as if it were a newly created model, it can't be updated, preserving the cache system intact. We will add this to our roadmap.

@thegeekywanderer thegeekywanderer linked a pull request Feb 19, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/schema Issues related with modeling and schema. area/services Issues related with api services and functionalities. feature request New feature or request
Projects
Status: Q4 2023 – Oct-Dec
Development

Successfully merging a pull request may close this issue.

5 participants