[Bug] Typescript highlight issue

Open
#876 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

No source file or test is named. Reproduce the supplied generic TypeScript example in VS Code with extensions disabled, then inspect the TypeScript grammar responsible for its highlighting. Done means the shown generic forms, including similar cases with generics, receive the expected highlighting.

Written by the indexing model from the issue text.

Description

bug enhancement You can do this

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version: 1.57.1
  • OS Version: Win10 19043.1052

Steps to Reproduce:

image

export type PageOptions<
  // eslint-disable-next-line @typescript-eslint/no-explicit-any
  Data extends Record<string, any>,
  // eslint-disable-next-line @typescript-eslint/no-explicit-any
  Custom extends Record<string, any>
> = (Custom &
  Partial<WechatMiniprogram.Page.Data<Data>> &
  Partial<WechatMiniprogram.Page.ILifetime & ExtendedPageLifeCycles> &
  Partial<ExtendedPageProperties> & {
    options?: WechatMiniprogram.Component.ComponentOptions;
  }) &
  ThisType<PageInstance<Data, Custom>>;

export interface PageConstructor {
  <
    // eslint-disable-next-line @typescript-eslint/no-explicit-any
    Data extends Record<string, any>,
    // eslint-disable-next-line @typescript-eslint/no-explicit-any
    Custom extends Record<string, any>
  >(
    name: string,
    options: PageOptions<Data, Custom>
  ): void;
}

I think this issue exist for quite a long time.

This may also happens in certain forms with generics.

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.