fix(dev): Fix linting for top-level scripts folder
#4977
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
size-limit report 📦
|
lobsterkatie
force-pushed
the
kmclb-fix-top-level-script-linting
branch
2 times, most recently
from
f876074 to
1032798
Compare
lobsterkatie
force-pushed
the
kmclb-fix-top-level-script-linting
branch
from
f711cdf to
79e7cad
Compare
lobsterkatie
force-pushed
the
kmclb-fix-top-level-script-linting
branch
from
79e7cad to
86372ce
Compare
lobsterkatie
force-pushed
the
7.x
branch
2 times, most recently
from
0040b0f to
299aeb3
Compare
lobsterkatie
force-pushed
the
kmclb-fix-top-level-script-linting
branch
from
86372ce to
6572ff9
Compare
AbhiPrasad
approved these changes
Apr 27, 2022
AbhiPrasad
pushed a commit
that referenced
this pull request
May 30, 2022
This is a follow up to #4963, which aimed to fix linting for `ts-node` scripts. That PR worked for `packages/*/scripts/*.ts`, but turned out not to work for the top-level `scripts/*.ts`, because the glob for file matching in the eslint config override matched both sets of scripts, but the tsconfig being pointed at only worked for package-level scripts. This fixes that by pulling the package-level linting override into the package-level `.eslintrc.js`, thus allowing the top-level override to apply only to the top-level scripts folder. Also, in order not to have to muck with the main repo `tsconfig` in any future changes/fixes, both sets of scripts now point to a new, dev-specific tsconfig for their linting. Finally, it fixes linting errors in the top-level `build:types:watch` script which were brought to light by the newly-fixed linting.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a follow up to #4963, which aimed to fix linting for
ts-nodescripts. That PR worked forpackages/*/scripts/*.ts, but turned out not to work for the top-levelscripts/*.ts, because the glob for file matching in the eslint config override matched both sets of scripts, but the tsconfig being pointed at only worked for package-level scripts. This fixes that by pulling the package-level linting override into the package-level.eslintrc.js, thus allowing the top-level override to apply only to the top-level scripts folder. Also, in order not to have to muck with the main repotsconfigin any future changes/fixes, both sets of scripts now point to a new, dev-specific tsconfig for their linting. Finally, it fixes linting errors in the top-levelbuild:types:watchscript which were brought to light by the newly-fixed linting.