Jacob Thomason

@ironexdev Sorry, I overlooked that you were including the actual query in the request string. I wasn't aware that was supported as part of the spec. In general, GraphQL APIs...

@ironexdev Can you submit a PR for this with tests? We probably just want to add a request method check, if the query string is being properly parsed already. ```php...

It's worth mentioning that a `description` attribute is currently supported by some annotations. It's needed on the following: - `Query` - `Mutation` - `Type` - `ExtendType` - `Factory`

@withinboredom Can you please describe this issue in more detail. What field middleware are you referring to, and in your example, what is it you're expecting to happen?

@withinboredom You're going to have to do a better job in explaining if you'd like some input on this. I still don't know what you're trying to do really.

Ah, thanks for the explanation. This is indeed poorly implemented at the moment. And not just in this scenario. There are multiple scenarios where the description isn't consistent across the...

@PhilippSchreiber did you figure out the issue here?

Wouldn't a `null` TTL value simply not expire the cache? How would specifying a TTL value, which expires the cache, improve performance?

I don't have an issue with, or see an issue, with exposing this property if you'd like to submit a PR. Maybe @moufmouf can chime in on this.

See https://github.com/doctrine/annotations/issues/443