Jayden Seric

@lydell > What counts as “supported”? Another level of "support" is for the ESLint plugin packages to have TypeScript types. I intend to have type-safe ESLint flat config in my...

This workaround appears to work: ```js // @ts-check import { existsSync } from "node:fs"; import { join, parse, resolve } from "node:path"; /** @type {import("next").NextConfig} */ export default { typescript:...

In the meantime, [`fake-tag`](https://github.com/jaydenseric/fake-tag) is a better solution than the copy-paste code [suggested in the readme](https://github.com/apollographql/eslint-plugin-graphql#identity-template-literal-tag): ```js import gql from 'fake-tag' const query = gql` { viewer { id }...

@rigelglen see the [`fake-tag` “Why not `String.raw`?” readme section](https://github.com/jaydenseric/fake-tag#why-not-stringraw): > This may be temptingly simple: > > ```js > const gql = String.raw > const QUERY = gql` > {...

@taletski I'm not sure exactly what you mean. Which repo/package are you referring to?

@taletski > So my questions is, do you plan to support the `gql()` function from the use case above? Support it in what repo/package? If you mean `eslint-plugin-graphql`, I'm not...

Because by widely adopted convention a JSDoc comment beginning with `/**` denotes a documentation comment, while `//` does not. This is for good reason; what if you do `// eslint-disable-next-line...

@mscdex can this contribution please be reviewed and hopefully merged? It's a small change-set relating to a bug yet has been open for 7 months now.

@markerikson > FWIW, I think this is why I've opted to bundle all of our artifacts for the Redux libs Never bundle modules that are published, that's a big anti-pattern....

It's important to be able to discriminate the ESLint code actions on save by ESLint rule. In VS Code, this is the config I use: ```json { "editor.codeActionsOnSave": { "source.fixAll.eslint":...