Repository navigation
"Unexpected PrivateIdentifier in name expression with literal-like access" being hit #48487
Description
Bug Report
🔎 Search Terms
"Unexpected PrivateIdentifier in name expression with literal-like access."
"Private Identifier"
"isSameEntityName"
"isPrivateIdentifier"
🕗 Version & Regression Information
I noticed this bug today (3/30/2022), but we believe that this bug goes back to Typescript 3.8
- This changed between versions 3.7.5 and 3.8.3
⏯ Playground Link
Playground link with relevant code
💻 Code
type SomeObj = {foo?: string};
class PrivateMemberBug {
#privateMember?: SomeObj;
someFunc() {
const someObj = this.#privateMember || {};
}
}This is a workaround I found:
type SomeObj = {foo?: string};
class PrivateMemberBug {
#privateMember?: SomeObj;
someFunc() {
const someObj: SomeObj = this.#privateMember || {};
}
}🙁 Actual behavior
Received cryptic error in console and no errors in vscode UI.
🙂 Expected behavior
No errors expected.
Activity
MartinJohns commentedon Mar 30, 2022
Private fields were only added with version 3.8, so how could it change between these two versions?
I'm also not sure what the issue is. This works fine, no errors.The error appears in the console of the playground.yipstanley commentedon Mar 30, 2022
My bad, I mean that 3.8 introduced this bug. I was following the format that fit the best in the issue template.
DanielRosenwasser commentedon Apr 4, 2022
Specific stack trace for searchers