Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Assert that we produce diagnostics in vscode. #229

Merged
merged 1 commit into from
Feb 3, 2022
Merged

Conversation

rictic
Copy link
Collaborator

@rictic rictic commented Feb 3, 2022

No description provided.

const config = vscode.workspace.getConfiguration();
config.update("lit-plugin.logging", "verbose", true);
config.update("lit-plugin.rules.no-missing-element-type-definition", "error", true);
const doc = await vscode.workspace.openTextDocument(vscode.Uri.file(path.join(__dirname, "../../src/test/fixtures/missing-elem-type.ts")));
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

break up long line? is there a formatter?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a formatter, but it's set to a hella long line length. Wanted to first land these test changes and check in on PRs, then do a commit to reformat everything.

return diagnostics;
}
// Is there a better way to wait for the ts server to be ready?
// Maybe we can listen for the event that displays and hides the "initializing TS/JS language features" message?
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🙏

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Eyeballing it, there's still a bit of time between that message going away and the diagnostics being available. Hm.

@rictic
Copy link
Collaborator Author

rictic commented Feb 3, 2022

(pair programmed with @43081j)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants