Replies: 1 comment 1 reply
-
I bought it up in this issue: #18231, which is still in discussions Currently, there is no standard convention about how we name it. The config inspector is doing colorization temporarily for better readability (both |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
According to the rfcs specification, flat config items can have
name
.https://github.com/eslint/rfcs/blob/main/designs/2019-config-simplification/README.md#the-eslintconfigjs-file
This is useful as debugging information for debugging tools such as eslint config inspector.
eslint config inspector is useful because it allows you to find each item as follows:
below is the case I used in
eslint-plugin-tailwindcss
that I am working on for PR:I have based the plugin name, colon and prefix on each item thing as name whether what is defined or not.
However, I am having issue with naming because there is no convention defined for naming.
In addition to my case, there is nuxt eslint, which uses
name
.https://github.com/nuxt/eslint/blob/main/packages/eslint-config/src/flat/configs/vue.ts
If there is already a best practice, I would like to know :)
Beta Was this translation helpful? Give feedback.
All reactions