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
GQL resolvers implement the same pattern of logging the arguments, binding the response in a let ninding, logging the response and returning. Example
Existing endpoints would be greatly simplified by adding an interceptor / middleware that logs those for every request
Implementation
Known steps towards feature implementation.
What needs further specifying and investigating.
Acceptance Criteria
argument and response logging middleware
resolvers cleaned of log calls
Notes
It is possible to replace the webserver with ring or yada if assignee deems it necessary. In such a case it would be nice to keep a GraphQL ide, for example with:
Problem
GQL resolvers implement the same pattern of logging the arguments, binding the response in a
let
ninding, logging the response and returning.Example
Existing endpoints would be greatly simplified by adding an interceptor / middleware that logs those for every request
Implementation
Known steps towards feature implementation.
What needs further specifying and investigating.
Acceptance Criteria
Notes
It is possible to replace the webserver with ring or yada if assignee deems it necessary. In such a case it would be nice to keep a GraphQL ide, for example with:
The text was updated successfully, but these errors were encountered: