no-unreachable-types based on Object type name

[ChrisPlease]

I'm fairly new to GraphQL, so I'm not sure if this is something I'm doing wrong. I have a project that I'd like linted, so I've added @graphql-eslint to the project for my gql files. I'm using the schema-recommended plugin.

I have a few types that are used for paginated queries, and as such are named PaginatedFoo. With the schema-recommended plugin, there's a rule strict-id-in-types, which I don't need for paginated queries, so I decided to take advantage of the exceptions.suffixes config and swapped the name FooPaginated and added Paginated to the excluded suffix.

Unfortunately changing the name of the type results in another error "Object type FooPaginated is unreachable.".

I only get the unreachable error when using Paginated suffix (this error happens for all of my paginated types).

This seems like a bug, but I'm so new to GraphQL and the tools around it, I thought I'd ask here first. The only way I've been able to get around this is to include the entire type in the exceptions object in the rule config, but then I have to update the config every time I add a new paginated query, when I should just be able to follow a naming convention using the suffix config option.

[ChrisPlease]

This looks like it might be VSCode. I restarted the ESLint server to no effect, but quitting VSCode and reopening seems to have resolved the error.