This repository was archived by the owner on Nov 16, 2023. It is now read-only.
This repository was archived by the owner on Nov 16, 2023. It is now read-only.
TSLint causes TS features to become unresponsive on incorrect react component syntax. #97
Closed
Description
I think I've got this broken down to the bare minimum number of steps to reproduce, and it's been happening for a while. I'm wondering if it's related to #55, but I can't guarantee that it is. It might be that this breaks on any sufficient number of TypeScript server errors, but here's the set of steps:
Environment: W10 (multiple editions)
VSCode version: All so far, including the latest insiders
TSLint version: 1.1.0
- create tslint.json and ./src/test.tsx files (source below)
- open src/test.tsx
- wait for language features to initialize
- go to the appropriately commented line
- enter a letter, delete, and repeat.
After a few times (reliably 5 times for me), the error underlines, outline, autocomplete, and other related features stop responding.
This behavior doesn't occur if the TSLint extension is disabled or not installed.
tslint.json:
{
"extends": ["tslint:recommended"]
}
test.tsx (NOTE: The outer div seems to be important here. Removing it prevents the crash):
const val: number = 1;
const Component = () => {
return (
<div>
{val === 0 ? (
"test"
) : (
// enter something here.
<div className={"something"}>
</div>
)}
</div>
);
};
export default Component;
Metadata
Metadata
Assignees
Labels
No labels