microsoft / microsoft/TypeScript

Font bug

Offen
#63,507 4 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Needs More Info
Vorherrschende Sprache
Go
Sterne
111k
Forks
14.3k
Ø Merge
2 T. 4 Std.
Gemergte PRs (30 T.)
132

Beschreibung

### 🔎 Search Terms

I was was changing the code font and after changing the font it came back on Cascadia everytime.

### 🕗 Version & Regression Information

- This changed between versions ______ and _______
- This changed in commit or PR _______
- 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

https://www.typescriptlang.org/play/?#code/C4TwDgpgBAyghgSxHAdlAvFA3gKClFOAWwgC4oBnYAJwRQHMBuPKMAewHcJryUBXIgCNuzfAAswvAcOqiCbakTgAbACbE49MgWkiWFPpGoBBYMDgBjANYARDVqlC9+OIoWOZLImwBuEEijAMJAQqh7cOAC+zDgAZnwoFsAIbGjKbPTwSKgAjAAUFIjIKDnkWcUAlNgsUBapFGzKEAB06fR5AAYAJFiF2SXNhCSRUGJwFKyc3FBNfspQPX3FOc3sXNQjdLCG0+WoAIQdFcyRODh1KFSURbllN2iYuPhD2gBEgHwbgNK7gKwbgGW734A63e+gCrd76AFt3AJlMrwANCw1txyDkAAwo1Gw8SSKA5ACsaJYKAUSjU9m0ACZsejKDsTGZLLYSeRcUjKa5vDwscyvL5-BBAsEIKFGZzomcLlclqhSXd+hhqs9iG9ALwbgFJdr4AcTYYxQgHSmGFwqbs5Go42cjHkcnGykExQqdRKBxQADspqpRlM5msdnt2hxKJZbnZuMp3j8ASCITCUAAHMLmGLgNd+gBmaXFWVPAgK8gfT6KwAsuwAFVCARYZAM8MisAUjt6-Dww0ml0SRGkpFB-GE20MqCt-AGN20z2d7FD-1sxEukM8vkR81+qLneoJiUoAAsqdQ6fxWagr0VgEUdxWAEj2AGoQLTmQCbDIAOhkAPwyAfoZAIVk1cm6zHJspjaxy7xz3bxO95GdSle24d06S9TRtCZF1WXcLFg25MN+UFKAv1hU540TYpsTXB45XwTMSGzPcABVqASKwKEfSkawNcgADZLRqUZMSNWd8PkG0-wg+iXR7alQIHf8oAATm7fCYLrXioAnRDpxE4V50uRd7jonCN3lQjtwAIT4ZRlDgJ9ayFd9MQAWmbF1rSJO1uLg-R+P7ekhOREdYNM1i2OkhDeXDAVIxyNC4gSJIUjSDI9hQUkCnuKVYHuKoMzFRoWjaTpFhiwYFRGMYJlrGYIDmBZegy2tNjQGBqTimVSUOY45xwNoIvyJccjqxqYui-pSTqoLEmSVIoFiBB6DEYBmvuUoquKaFMMlHCEpYJKmlaDJOhgGAACksSKlrMuGKAEAmIaRuSBhFUAUp3YE2qBSR2jKXkiGbBD4BMODEEAAH4jn0CbmgkWVdv+0yoE64pSUGX8bK0KBgd2iSKh+-oVn+zBAbAGHZsi5pgJpD0nIgxb6mSlb2g6dattu9Kur2iARjgRyjoQagrjEaBVAgFQJjgKBBGGnn0g4C6oGANgrq2nI7qRmnImaKANSsPhRnGSXlj+sBsvRppYmAWr6viPrQsG4bRqipcUym1AZqXVcLZQBb8CWlLVrJ66Jap4ok2lg7GZOuh6CF8ntvd1Bl2l3We3uUOUcxqP0eBvJQdQT2rI7b0oAAKhuqpYcj5p4cJy5idSjotLYNgiAu-YxaD4rky9+m8cZ5mE0Dt3a+KUOHuFuArAgLnRgQYBK6gAAJQ7mO9lWQ7VyJvtOY7RvGpGrZihGF+AU37iTFf+mXCogA

### 💻 Code

```ts
type Saiyan = {
name: string;
power: number;
hp: number;
normaldamage: number;
superAttackDamage: number;
armor: number
movementSpeed: number
};

function logSaiyan1(saiyan1: Saiyan) {
console.log(`${saiyan1.name} has power level ${saiyan1.power} in Super Saiyan!`);
}

const saiyan1: Saiyan = {
name: "🥋𝖦𝖮𝖪𝖴㊙",
power: 1000000,
hp: 15000,
normaldamage: 25,
superAttackDamage: 500,
armor: 10,
movementSpeed: 50,
};

const saiyan2: Saiyan = {
name: "🔥🥋Gohan㊗",
power: 1000000000,
hp: 250000,
normaldamage: 70,
superAttackDamage: 1500,
armor: 50,
movementSpeed: 80,
};
const saiyan3: Saiyan = {
name: "🥋🔴Panパン👊",
power: 1000000,
hp: 12050,
normaldamage: 50,
superAttackDamage: 555,
armor: 10,
movementSpeed: 200,
}
const saiyan4: Saiyan = {
name: "👑😤Vegetaベジータ⚡",
power: 1000000,
hp: 14000,
normaldamage: 70,
superAttackDamage: 5000,
armor: 1,
movementSpeed: 40,
}
const saiyan5: Saiyan = {
name: "👑Trunks⚡",
power: 60000,
hp: 10000,
normaldamage: 60,
superAttackDamage: 950,
armor: 100,
movementSpeed: 90,
}
const saiyan6: Saiyan = {
name: "Bulla",
power: 50,
hp: -200,
normaldamage: 1,
superAttackDamage: 10,
armor: -100000,
movementSpeed: 1,
}
function logSaiyan2(saiyan2: Saiyan) {
console.log(`${saiyan2.name} has power level ${saiyan2.power} in Super Saiyan 2!`);
}

logSaiyan1(saiyan1);
logSaiyan2(saiyan2);

function fight1(saiyan1: Saiyan, saiyan2: Saiyan) {
console.log(`SSJ 1 ${saiyan1.name} is fighting💥 SSJ 2 ${saiyan2.name}, but why?`)
saiyan1.hp = saiyan1.hp - (saiyan2.normaldamage - saiyan1.armor)
saiyan1.hp = saiyan1.hp - saiyan2.superAttackDamage
console.log(`SSJ 2 ${saiyan2.name} attacks first he deals a big blow💥 to SSJ 1 ${saiyan1.name}. Goku has ${saiyan1.hp} hp left!`)
}

function fight2(saiyan3: Saiyan, saiyan4: Saiyan) {
console.log(`SSJ 1 ${saiyan3.name} is fighting💥 SSJ 1 ${saiyan4.name}!`)
saiyan4.hp = saiyan4.hp - ((saiyan3.normaldamage * 2) - saiyan4.armor)
console.log(`Boom💥! SSJ 1 ${saiyan3.name} attacks first SSJ 1 ${saiyan4.name} takes a hit💥! His hp is ${saiyan4.hp}`)
}
fight1(saiyan1, saiyan2)
fight2(saiyan3, saiyan4)
```

### 🙁 Actual behavior

The font remained the same when I tried to change it.

### 🙂 Expected behavior

The font would change because the name of the feature is code font .

### Additional information about the issue

_No response_

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Rechercherichtung

Öffne das verlinkte TypeScript Playground und reproduziere das Problem, indem du die Code-Schriftart mit dem bereitgestellten Beispiel änderst. Überprüfe, ob die ausgewählte Schriftart angewendet wird oder zu Cascadia zurückkehrt, und betrachte den Bericht als abgeschlossen, wenn die Änderung der Code-Schriftart im Playground sichtbar bestehen bleibt.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
typescript
Bereich
frontend
Issue-Typ
Bug
Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Aktivitätsstatus
Ruhig
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
45/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.