Skip to content

Depreciated warning in the wrong place #117745

Closed
@thebinarysearchtree

Description

@thebinarysearchtree

When writing javascript, vscode will put a strike through depreciated words found in object literal property declarations such as const p = { name until the colon is added. This seems like it is checking in the wrong place for this type of error as there are no depreciated words in this context.

Metadata

Metadata

Assignees

Labels

*duplicateIssue identified as a duplicate of another issue(s)javascriptJavaScript support issues

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions