redhat-developer / redhat-developer/vscode-xml
Address the "no explicit any" warnings from eslint
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 328
- Forks
- 101
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 7
Description
I will create another issue to address the "no explicit any" warnings in a future PR (time permitting), since it's usually a better idea to not add a type than to add
any.
I also think it might be okay to switch the warnings to errors after all of the existing markers have been fixed.
Originally posted by @datho7561 in https://github.com/redhat-developer/vscode-xml/pull/948#discussion_r1395904937
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
The issue names ESLint's no-explicit-any warnings but does not identify files, tests, or an entry point. Start by locating the existing warning markers in the TypeScript code and confirming the lint command; done means the existing warnings are addressed, with the rule's severity considered afterward.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- eslint, typescript
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100