Skip to content

JSON and JSDoc updates #37

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

Merged
merged 3 commits into from
Mar 8, 2023
Merged

JSON and JSDoc updates #37

merged 3 commits into from
Mar 8, 2023

Conversation

FSVetaz
Copy link
Contributor

@FSVetaz FSVetaz commented Mar 7, 2023

No one in the org uses JSDocs' rules from here currently. Tree Web team uses the config in their additional config so it would be good to just have the jsdoc rules in one place and tree team extend frontier's JSdocs' rules.

image

Put json config in an override for .json files mainly because then json files are linted by default (npx eslint .) instead of explicitly linting for that extension (npx eslint . --ext .json) See https://eslint.org/docs/latest/use/command-line-interface#--ext

FSVetaz added 3 commits March 7, 2023 16:33
This just makes it so that doing `npx eslint .` it will include json files in the linting since it is in the overrides.

https://eslint.org/docs/latest/use/command-line-interface#--ext "Default Value: .js and the files that match the overrides entries of your configuration."
@joeycozza
Copy link
Collaborator

I didn't know about using the overrides for other extensions to automatically get them. That is nice. Thanks.

@joeycozza joeycozza merged commit 3a0aab4 into master Mar 8, 2023
@joeycozza joeycozza deleted the jordi/more-upds branch March 8, 2023 16:45
FSVetaz added a commit to fs-webdev/eslint-config-tree that referenced this pull request Mar 8, 2023
FSVetaz added a commit to fs-webdev/eslint-config-tree that referenced this pull request Mar 8, 2023
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.

2 participants