Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add configs #23

Merged
merged 7 commits into from
Jun 23, 2024
Merged

Add configs #23

merged 7 commits into from
Jun 23, 2024

Conversation

fregante
Copy link
Contributor

@fregante fregante commented Nov 25, 2023

Closes #22

Missing:

  • I haven't tried this yet
  • Add mention to readme

Copy link
Contributor Author

@fregante fregante left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested and it seems to work

"plugin:local-rules/error"
]
}
```
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added this on top because I think that it's the most common usage and it has the least amount of config

@fregante fregante marked this pull request as ready for review November 25, 2023 06:10
index.js Outdated
@@ -26,6 +26,18 @@ if (!rules) {
);
}

function getConfig(type) {
return {
rules: Object.fromEntries(Object.keys(rules).map((rule) => {
Copy link
Contributor Author

@fregante fregante Nov 25, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Object.fromEntries is Node 12+ by the way.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for calling this out! I'll make this a major version change.

Copy link
Owner

@cletusw cletusw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Just a few requested changes.

index.js Outdated
@@ -26,6 +26,19 @@ if (!rules) {
);
}

function getConfig(type) {
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Update style to match

  • " -> '
  • add semicolons
  • add trailing commas

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be good to set up linting and CI in this repo to enforce this kind of rules 😁

Done

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[[hejckxk'x

index.js Outdated
module.exports = {
configs: {
error: getConfig("error"),
warn: getConfig("warn"),
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's rename this to 'all-warn'.

That said, as an aside, severity "warn"

is typically used when introducing a new rule that will eventually be set to "error"

(source)

So I'm not sure how common it is to want everything to be warn.

I think a useful follow-on PR would be to add support for an optional severity field inside rules' docs field (since plugins are allowed to put whatever they want there) that getConfig would check first and use the value of that field when present, allowing individual rules to set themselves to warn while the rest are still error.

module.exports = {
  'disallow-identifiers': {
    meta: {
      docs: {
        description: 'disallow identifiers',
        category: 'Possible Errors',
        severity: 'warn',
      },

index.js Outdated Show resolved Hide resolved
index.js Outdated
module.exports = {
configs: {
error: getConfig("error"),
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's rename error to all. It looks to be normal for all to set all rules to severity error: https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/src/configs/all.ts

@cletusw
Copy link
Owner

cletusw commented Nov 25, 2023

Sorry for the early review! Wasn't aware of the "ready for review" feature.

@fregante
Copy link
Contributor Author

fregante commented Dec 4, 2023

Should be all done

@fregante
Copy link
Contributor Author

How can we move this forward?

@cletusw cletusw merged commit 063ceda into cletusw:master Jun 23, 2024
@cletusw
Copy link
Owner

cletusw commented Jun 23, 2024

Sorry for the ridiculous delay. Thank you!

@fregante fregante deleted the patch-1 branch June 23, 2024 04:28
@fregante
Copy link
Contributor Author

Thank you for the merge!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add all config to automatically load all rules at error level
3 participants