-
Notifications
You must be signed in to change notification settings - Fork 7
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
Response interceptor is not working in database. #167
Comments
Hello, @stasguma. Thanks for using mock-config-server! Our team is currently discussing the possibility of implementing interceptors for database. We will keep you in touch. |
…etabase api interceptors, add baseUrl field for database
# Conflicts: # src/core/database/createDatabaseRoutes/helpers/createNestedDatabaseRoutes/createNestedDatabaseRoutes.ts # src/core/database/createDatabaseRoutes/helpers/createShallowDatabaseRoutes/createShallowDatabaseRoutes.ts
…createGraphQLMockServer, remove call response interceptors for __db and __routes routes, add missing call response interceptors for post routes, set data to null in delete route
Hello, @stasguma. We decided to completely rework the logic of working with the database and with interceptors in particular in version 5.0.0. So the fix for this issue will not be merged into the release. Database interceptors calls were added in this MR. If you need them, you can fork the repository and merge these changes as a temporary solution. |
Can you explain why the response interceptor is not invoked? Did I miss something? API call works fine.
The text was updated successfully, but these errors were encountered: