Version 5.0.0

[znarf]

Given that graphql-eslint is currently not a suitable replacement and that this plugin has not been updated in 3 years, I'm proposing the following maintenance release.

I made great care of modifying the strict minimum for that purpose and kept things simple.

Dropping compatibility with various version of Node, Eslint and GraphQL is due to dependencies own compatibilities.

I hope it can be accepted and published to npm, or that someone can invite me to do so. If that's not possible, I'll publish it as @opencollective/eslint-plugin-graphql.

---

Upgrade all dependencies and compatibility with latest Eslint and GraphQL.

• upgrade all dependencies to their latest version
• remove pretty-quick and husky (was misconfigured)
• ensure compatibility with Eslint 7 and 8
• ensure compatibility with GraphQL 16

Breaking changes:

• drop compatibility with Node.js < 16
• drop compatibility with GraphQL < 14.2
• drop compatibility with Eslint < 7

[jerelmiller]

Hey @znarf 👋

Would you mind giving a bit more detail about what you shared here?

Given that graphql-eslint is currently not a suitable replacement

We are very likely to fully deprecate eslint-plugin-graphql in the near future and this statement caught my eye.

Edit: Fixed the reference to the wrong package name

[JounQin]

@jerelmiller

We are very likely to fully deprecate graphql-eslint in the near future

I suppose you mean deprecate eslint-plugin-graphql?

[jerelmiller]

@JounQin oops yes thats what I meant. I read graphql-eslint as I was typing that message and wrote the wrong thing 😭. Thanks for the correction!

[znarf]

@jerelmiller Based on your feedback, I had yet another look at graphql-eslint today and it seems I got it wrong. It's now indeed covering rules like no-deprecated or fields-on-correct-type which were our main use cases.

If I remember, I think I got stuck migrating our slightly complex setup and was missing migration guidelines.

There are still some gotchas when using multiple schemas, but it should ultimately work.

While this PR was carefully crafted and ready to go, I now understand it would send the wrong message to release a new version.

Closing!

[znarf]

Fyi, we're actually blocked because @graphql-eslint doesn't seem to support the feature mentioned here as Additional Schemas or Tags

This plugin can be used to validate against multiple schemas by identifying them with different tags.

[JounQin]

I think you should post a feature request or PR even better for graphql-eslint.

[jerelmiller]

@znarf good to know! We are going to be in contact with the owners of that package (The Guild) before we deprecate, so this is an item we can take note of in that discussion.

As @JounQin said, I'd highly encourage you at the very least to open a feature request over there as well to know there is community interest in that feature.

[znarf]

Sure, I'll provide at least a test case. I started to have a look at implementation but the PR is a bit of a longshot.

[dimaMachina]

@znarf Hi, I am the maintainer of GraphQL-ESLint

GraphQL-ESLint has the support for additional schemas 🙂. It’s not described in docs but described in github examples.
Here is working example for future v4 or for current v3

I plan to rewrite graphql-eslint docs and describe the use of multiple schemas too! Also, all roadmap for v4 is done, and first 4.alpha was released. Actually, the missing part to release v4 is to update docs 😅

[znarf]

@dimaMachina Thank you for jumping there! Our use case is actually multiple schemas BUT in the same file. I have studied the docs and the code and it doesn't look possible.

I started exploring that support here: https://github.com/opencollective/graphql-eslint/pull/1/files