GraphQL

If you PATCHed to /posts/1, but send payload with a different id:

{
  data: {
    id: 789,
    type: 'posts',
    attributes: { ... }
  }
}

We pay attention to the payload and not the URL - instead let's throw an error when there is a mismatch.

Describe the bug
The Course export card UI is broken if tags are included.

To Reproduce
Steps to reproduce the behavior:

1. Go to Admin
2. Click on Course then select the course
3. Click on Create New Exports
4. Add multiple tags and click on exports

Expected behavior
The download button should be placed properly

Screenshots
![image](https://user-images.githubus

Hey,

I think it would be great to have extensions with code (see here: http://graphql-ruby.org/errors/execution_errors.html) to the Graphlient::Errors::ExecutionError class.

So it could be used in tests as:

rescue Graphlient::Errors::ExecutionError => e
  expect(e.message).to eq('My error message')
  expect(e.extensions.code).to eq('UNAUTHORIZED')
end

Rails controller has a method `"rescue_from" which allows customizing response when a specific error happens. It would be nice to have the same feature for GraphqlRails controllers. This would enable sharing logic between rails and graphql_rails controllers easier.

Hey guys not sure if this is still maintained, for some reason running rubocop -a is throwing several
GraphQL/ExtractInputType errors inside of an input type object

example of the error:

app/graphql/types/public/program_application_attributes.rb:11:7: C: GraphQL/ExtractInputType: Consider moving arguments to a new input type
      argument :company_size, String, required: false, descri

I am trying to use both fragment caching + action policy and due to lack of documentation I am unable to make it work if I have a authorized_scope: true if my field

if I have a field like this:
field :collections, [CollectionType], null: false, authorized_scope: true, cache_fragment: { context_key: :current_user } do

I get an error:

Couldn't find policy class for.... "Could