Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Be less strict about which characters can appear in a JSDoc property name

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
tooling

Research direction

Start with the TypeScript and JavaScript grammar extension linked in the issue and reproduce the JSDoc examples shown. Trace how property names are parsed, then verify that @baz and even#ThisShouldBeAValidName! are each treated as single names and appear in IntelliSense.

Written by the indexing model from the issue text.

Description

Accepting PRs help wanted

From https://github.com/microsoft/TypeScript/issues/36047

TS and JS Grammar Extension version: 0.0.53 / latest

Code

/**
 * @typedef Foo
 * @property {string} bar Property shows in intellisense
 * @property {string} @baz Property should show in intellisense but does not
 * @property {string} even#ThisShouldBeAValidName! But the name is not parsed as expeted
 */

Bug
@baz and even#ThisShouldBeAValidName! are not parsed as single property names

Dominant language
TypeScript
Stars
471
Forks
149
No merged PRs in 30d

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.

More from microsoft/TypeScript-TmLanguage

All issues in microsoft/TypeScript-TmLanguage

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.