-
Notifications
You must be signed in to change notification settings - Fork 3
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
Reflect changes after content adjustments #14
Comments
It's the expected behavior, but related to one thing - saving a time. I just didn't have time to write a file watcher etc., that's why it requires to restart dev server every time you change the content. Although there is an option to get file watcher for free, use |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I request a entity or collection and then I change content in the content directory (e.g. I change a title of a collection item). This change will not be displayed in the result when I request the API again.
The change is only displayed in the API response when I have restarted the node server (-> nom run dev).
Is this a desired behavior or is there a way to change the content and make this change visible immediately to the API?
The text was updated successfully, but these errors were encountered: