-
-
Notifications
You must be signed in to change notification settings - Fork 69
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
Feature/graphql #166
base: beta
Are you sure you want to change the base?
Feature/graphql #166
Conversation
I added graphql route that essentially has a relay middleware that transforms requests in the way that allows us to use existing controllers initially created for REST. This way we wound't have to worry about synchronizing REST vs graphql in case we change/add additional behaviors to controllers. @gitfrosh I just want you to see the approach, in case you approve it, I will promptly add pagination params in the request arguments + auth middleware |
pagination and authorization added ✅ |
this addresses issue #16 |
add graphql support to all existing routes