You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: