oxc-project / oxc-project/backlog

Opportunities to enhance current lint rules with types

Open
#164 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
7
Forks
0
PR merge metrics
No merged PRs in 30d

Description

This is not something that should be picked up: this is a list of rules that could be enhanced if/when we decide to implement type information as part of linting.

  • no-extra-boolean-cast
    • Fix any Boolean(x) into x if the type of x is boolean
  • unicorn/require-post-message-target-origin
    • Only fix foo.postMessage(msg) into foo.postMessage(msg, origin) if the postMessage method has a second argument

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the two listed rules, no-extra-boolean-cast and unicorn/require-post-message-target-origin, along with the stated type-information requirement. Done would mean deciding whether and how type-aware linting should enable the two proposed enhancements; this issue explicitly says it is not ready to be picked up.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.