Implemented #8. Both @deprecated(reason: String), or an empty @deprec…

[acidbluebriggs]

@deprecated directive can be used within the schema definition and the messages will now be available when a client introspects the schema for deprecated values. The README.md has also been updated to reflect the new addition.

[apottere]

http://i0.kym-cdn.com/entries/icons/original/000/004/815/lol-guy.jpg

[apottere]

It looks like this is only applied to enum values - we'll probably have to expand it in the future to work on fields/arguments.

[acidbluebriggs]

It's on fields also. You can see it on this line.
I just didn't create a new entry in the readme for that example. I just kept in line with your @doc example.

I'm not 100% sure that arguments are valid deprecation targets. I thought when I read the spec earlier it stated only enums and fields. I'll double check.

According to: http://facebook.github.io/graphql/#sec-Deprecation

Deprecation

To support the management of backwards compatibility, GraphQL fields and enum values can indicate whether or not they are deprecated (isDeprecated: Boolean) and a description of why it is deprecated (deprecationReason: String).

I see no option in the main GraphQL-Java api to deprecate an argument.

I should have worked on some sort of test, but that would have been a lot of work I couldn't get in quickly enough as there are no client tests in there at the moment and I really don't know much about the groovy testing framework. I was looking for one that tested the @doc directive, but there wasn't one.

[apottere]

Ah, I totally missed that line, sorry. I also wasn't aware that arguments didn't support deprecation - when the introspection query comes back, arguments have keys for isDeprecated and deprecationReason but that's probably just from their parent class.

I can add a test that checks the generated schema for deprecation messages tomorrow.

Thanks!