-
Notifications
You must be signed in to change notification settings - Fork 5
Uses pipeline #24
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
Uses pipeline #24
Conversation
Hi! Are there any updates? When do you think you can make next release? |
The code seems to work, but I need to make some additional tests to be sure all cases are managed. I need more time :) |
Is it possible to use something like AuthMiddleware with this pipeline idea? E.g. I want that some Transformer are only accessible, when user is logged in. Or is there any other option to achieve this? In graphql-library from rebing there was an option to add middlewares to whole schemas, so it is possible to define an "open" and "protected" schemas. |
You cannot use |
The main goal here is to use pipeline instead of modifying transformers :
This branch will not remove transformers at all, only the underlying code : it will only calls the pipeline and returns the result. To manage custom transformers, a configuration will be set to manage each new transformer (like #22).