Skip to content

Conversation

@KyleAMathews
Copy link
Contributor

No description provided.

@gatsbybot
Copy link
Collaborator

gatsbybot commented Jun 15, 2017

Deploy preview ready!

Built with commit 47955d0

https://deploy-preview-1177--using-drupal.netlify.com

@gatsbybot
Copy link
Collaborator

gatsbybot commented Jun 15, 2017

Deploy preview ready!

Built with commit 47955d0

https://deploy-preview-1177--gatsbygram.netlify.com

@gatsbybot
Copy link
Collaborator

gatsbybot commented Jun 15, 2017

Deploy preview failed.

Built with commit 47955d0

https://app.netlify.com/sites/gatsbyjs/deploys/5942d8c3cf321c4b3c3f1a33

…ilter'

This both makes it easier to navigate the connection arguments as well
as protects against name collisions as if someone had a filter named
skip, limit, or sort (the other top-level input fields) then there'd be
a mysterious error.
@KyleAMathews
Copy link
Contributor Author

I also decided to rename the connection field "groupBy" to group for the same reason as sortBy -> sort.

@KyleAMathews
Copy link
Contributor Author

From the last commit, more of the rational for the filter change:

This change both makes it easier to navigate the connection arguments as well
as protects against name collisions as if someone had a filter named
skip, limit, or sort (the other top-level input fields) then there'd be
a mysterious error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants