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

Add ability to re-generate schemas as required. #127

Open
Tracked by #342 ...
Decipher opened this issue May 25, 2020 · 0 comments
Open
Tracked by #342 ...

Add ability to re-generate schemas as required. #127

Decipher opened this issue May 25, 2020 · 0 comments
Assignees
Labels
enhancement New feature or request module: schema Related to the `druxt-schema` module
Milestone

Comments

@Decipher
Copy link
Member

As a developer I don't want to restart my frontend every time the backend display modes are updated.

Currently the schema is only generated on first run/build. This means that if the Display modes are updated in the backend while the Frontend server is running the schema will not reflect the active backend configuration.

Due to the current permissions required for druxt-schema, this will either require authentication, restricting usage to developers, or a Read-only permission in the backend.

@Decipher Decipher self-assigned this May 25, 2020
@Decipher Decipher transferred this issue from another repository Aug 14, 2021
@Decipher Decipher added enhancement New feature or request module: schema Related to the `druxt-schema` module labels Aug 26, 2021
Decipher added a commit that referenced this issue Oct 31, 2021
@Decipher Decipher added this to the 1.2.0 milestone Jun 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request module: schema Related to the `druxt-schema` module
Projects
None yet
Development

No branches or pull requests

1 participant