Field argument names conflict with constructor arguments

The current implementation of Field’s constructor handles arguments named name or source that are of Argument type but does not do the same for the rest of them (e.g. description or required).

For example, this fails as follows:

import graphene

class Query(graphene.ObjectType):
    answer = graphene.Int(description=graphene.Int())
    def resolve_answer(self, info, description):
        return description

schema = graphene.Schema(query=Query)
result = schema.execute('{ answer(description: 42) }')

assert result.data
assert result.data['answer'] == 42

[tdiam]

I’m having second thoughts on this.

The use case can actually be handled by:

answer = graphene.Int(args={'description': graphene.Int()})

Checking all the “metadata arguments” in Field’s constructor does not seem scalable (it would be 8 if’s with the current signature). A simple mention in the docs that arguments with “reserved” names can be specified in args instead would probably suffice.

[jkimbo]

PR created to update docs: https://github.com/graphql-python/graphene/pull/1170