Eslint Updates #1322
Merged
Eslint Updates #1322
Conversation
This file contains 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
- warning 'meta' is defined but never used - warning 'samples' is assigned a value but never used
- error Use object destructuring prefer-destructuring
- Unnecessary escape character: \/ no-useless-escape
- 'full' is defined but never used @typescript-eslint/no-unused-vars
- Unexpected empty object pattern no-empty-pattern
joshsadam
added
UI
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.
Description of changes
Added
lintcommand to yarn scripts to facilitate faster and easier linting of js/ts code.Added eslint rule to check for object and array restructuring.
Fixed some of the eslint errors.
Related issue
Link to the GitHub issue this pull request addresses using the
#issuenumformat. If it completes an issue, useFixes #issuenumto automatically close the issue.Checklist
Things for the developer to confirm they've done before the PR should be accepted:
Tests added (or description of how to test) for any new features.User documentation updated for UI or technical changes.