Benedikt Franke

```php $resolveInfo->getFieldSelection(100); ``` That is absolutely fine, if it has the information you need. `lookAhead()` gives you more detailed information about the selection, such as the types of the sub-fields...

I think those questions are off-topic, you may ask in StackOverflow or Slack.

Duplicate of https://github.com/BenSampo/laravel-enum/issues/245

I believe this PR would break the existing translations entirely, so it is not something we can merge and release in the current major version.

I don't understand entirely what changes would be necessary for users of this library to adapt to this change. Can you describe in `UPGRADE.md`?

Closing due to lack of response.

Closing, as I no longer plan to develop this library further - see https://github.com/BenSampo/laravel-enum/issues/332.

When used as an object, `EnumValue` falls back to the same translation key as the pipe syntax based rule. It just requires that the language files were published.

Closing, as I no longer plan to develop this library further - see https://github.com/BenSampo/laravel-enum/issues/332.

I was actually surprised to learn that GraphQL allows for covariant subtyping when implementing interfaces. Nice! The schema you propose would be optimal, but it might be hard to construct...