-
Notifications
You must be signed in to change notification settings - Fork 2.8k
remove support for query templates #2560
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
Conversation
|
Deploy preview for hasura-docs ready! Built with commit ecb427a |
|
Review app for commit 5f0455c deployed to Heroku: https://hge-ci-pull-2560.herokuapp.com |
query templates is a little known feature that lets you template rql queries and serve them as rest apis. This is not relevant anymore given the GraphQL interface and getting rid of it reduces the dev time when adding features in few subsystems. This feature has never been used outside hasura's internal projects or documented or exposed through console and hence can safely be removed.
|
Review app for commit 3120fff deployed to Heroku: https://hge-ci-pull-2560.herokuapp.com |
rakeshkky
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
server LGTM
|
Review app for commit 2842ad0 deployed to Heroku: https://hge-ci-pull-2560.herokuapp.com |
|
Review app for commit ecb427a deployed to Heroku: https://hge-ci-pull-2560.herokuapp.com |
|
Review app https://hge-ci-pull-2560.herokuapp.com is deleted |
query templates is a little known feature that lets you template rql queries and serve them as rest apis. This is not relevant anymore given the GraphQL interface and getting rid of it reduces the dev time when adding features in few subsystems. This feature has never been used outside hasura's internal projects or documented or exposed through console and hence can safely be removed.
query templates is a little known feature that lets you template rql queries and serve them as rest apis. This is not relevant anymore given the GraphQL interface and getting rid of it reduces the dev
time when adding features in few subsystems.
This feature has not been used outside hasura's internal projects or documented or exposed through console and hence can safely be removed.
Affected components