Lint warnings
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 172
- Forks
- 109
- PR merge metrics
- No merged PRs in 30d
Description
## Description
There are 32 warnings after going through a lint check. Removing the warnings will help in improving the current code.
## Expected Behavior
No warnings
## Actual Behavior
32 warnings
## Steps to Reproduce the Problem
1. In the source folder run `yarn run lint`
## Screenshots
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the repository's source folder by running `yarn run lint` and reviewing the 32 warnings shown by the lint check. Identify the files and warning categories from the command output; done means the lint run reports no warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100