microsoft / microsoft/TypeScript

Enable JavaScript specific warning behavior

Open
#6,802 3 comments 13 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Committed Domain: JavaScript Suggestion VS Code Tracked
Dominant language
Go
Stars
111k
Forks
14.3k
Avg merge
2d 4h
Merged PRs (30d)
132

Description

See #6658 for background.

Currently for JavaScript files we provide a very limited set of errors, mostly for syntax errors. There are a number of grammatical and type errors that would be useful to display also.

Brief notes from ad hoc discussion in the team room include:

  • Move the code that flags TypeScript syntax in JavaScript files for better error handling
  • Add a distinction between errors and warnings to avoid "valid" JavaScript containing errors
  • Make the warnings user configurable as part of the project (i.e. may enable/disable certain warnings)

More detailed design to come...

Contributor guide

Open the contributing guide

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

Start by reading issue #6658 and reviewing the current JavaScript diagnostic behavior. The notes identify TypeScript-syntax handling, error-versus-warning distinctions, and project-configurable warnings as areas to scope; completion requires a settled design before implementation can be considered done.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, typescript
Domain
compilers
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.