linting errors since past how many commits not sure #181
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.
As discussed yesterday , i was fixing 130 Typescript linting errors , which I fixed in 1 or 2 hours
most of the errors were caught using
npm run lintitself , but after Typescript errors are first caughttsc --noEmitnext it went to ESLint errors.
the errors jumped to 3000 errors (ESLint Errors)
Initially it i changed only 6 test files that had Typescript linting errors
now it skyrocketed to 73 files , could be more i havent finished fixing the linting errors
should i continue with this? i will keep this as an draft for now
Cheers,
Dibby