oasisprotocol / oasisprotocol/docs
Fix open warnings from linter
Open
Nobody has claimed this yet.
good first issue
help wanted
- Dominant language
- TypeScript
- Stars
- 15
- Forks
- 46
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 1
Description
Right now there are far over 100 warnings if you run the linter.
There should be a cleanup be done, that new warnings won't get lost in all the old warnings
Contributor guide
No contributing guide indexed for this repository
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 by running the repository's linter and reviewing the more than 100 existing warnings. Identify which files and warning categories are involved, then clean up the reported issues so the remaining output is manageable and future warnings are not obscured.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100