microsoft / microsoft/TypeScript

Error TS4020 or TS4023, working with mixins, base class has static symbol property, only when multiple files.

Ouverte
#52,644 2 commentaires 2 réactions 1 personne assignée Voir sur GitHub

@weswigham y travaille déjà.

Depuis le 17/2/2023.

Needs Investigation Rescheduled
Langage dominant
Go
Étoiles
111k
Forks
14.4k
Merge moyen
1 j 19 h
PR mergées (30 j)
117

Description

Bug Report

In the following code (file: index.ts)

export class TestComponent extends MixinComponent(Component<HTMLElement>)<number> {
}

I get error TS4020: 'extends' clause of exported class 'TestComponent' has or is using private name 'Test'.

I've gotten that error before and managed to fix it by exporting the "private name" the compiler is complaining about.

But in this case, said name IS being exported (file: component.decl.ts)

export const Test = Symbol("test");  // <--- HERE

export declare abstract class Component<T extends HTMLElement = HTMLElement> {
  readonly element: T;

  public static [Test]: string;
}

What other reason is there to cause this error? I don't see no "private name".

It's also a different error Exported variable 'MixinParent' has or is using name 'Test' from external module "/sandbox/component.decl" but cannot be named. if I put the inheritance in two separate lines (file: index.ts)

export const MixinParent = MixinComponent(Component<HTMLElement>);

export class AnotherTestComponent extends MixinParent<string> {
}
🔎 Search Terms

all in title.

🕗 Version & Regression Information

latest.
(declaration: true)

⏯ Playground Link

codesandbox.io link

in playground is not reproducible, I suppose because everything is in a single file, but here's a link anyway.

Playground link

💻 Code

above.

🙁 Actual behavior

errors.

🙂 Expected behavior

no errors.

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.