(2 Kommentare) (0 Reaktionen) (0 zugewiesene Personen)TypeScript (6.726 Forks)batch import

BugDomain: enumHelp Wanted

Repository-Metriken

Stars: (48.455 Stars)
PR-Merge-Metriken: (Durchschn. Merge 6T 17h) (9 gemergte PRs in 30 T)

Beschreibung

Bug Report

2023-07-31T08:27:10.000Z

# Bug Report ### 🔎 Search Terms - const enum ### 🕗 Version & Regression Information  - This is a runtime crash - This changed between versions 4.4.4 and 4.3.5 - This is the behavior in every version I tried, and I reviewed the FAQ for entries about _________ - I was unable to test this on prior versions because _________ ### ⏯ Playground Link [Playground link with relevant code](https://www.typescriptlang.org/play?ts=5.1.6#code/MYewdgzgLgBApmArgWxgMRCGBvAUDAmAQxgF4YBGAGlwF9ddRIQAbOAOhZAHMAKDEAG0ARBWEBdAJRA) ### 💻 Code ```ts const enum Foo { a = 1, } console.log(Foo["1"]) ``` ### 🙁 Actual behavior ```JavaScript console.log(Foo["1"]); ``` ### 🙂 Expected behavior ```JavaScript console.log("a"); ``` or report error.

🔎 Search Terms

const enum

🕗 Version & Regression Information

This is a runtime crash
This changed between versions 4.4.4 and 4.3.5
This is the behavior in every version I tried, and I reviewed the FAQ for entries about _________
I was unable to test this on prior versions because _________

⏯ Playground Link

Playground link with relevant code

💻 Code

const enum Foo {
    a = 1,
}

console.log(Foo["1"])

🙁 Actual behavior

console.log(Foo["1"]);

🙂 Expected behavior

console.log("a");

or report error.

Contributor Guide

Research-Richtung: Untersuche das ausgegebene JavaScript für const enums und die Reverse Mapping Implementierung, um zu verstehen, warum Foo['1'] einen ReferenceError verursacht.
Tech Stack: typescript
Domain: compilers
Issue Type: Fehler
Schwierigkeit: 2
Geschätzte Zeit: 1-3 Stunden
Aktivitätsstatus: Aktiv
Klarheit: Klar
Voraussetzungen: TypeScript
Einsteigerfreundlichkeit: 70