Skip to content

Comments

feat(oxc_language_server): Publish a message when there are UnknownRules errors building the LinterBuilder#7087

Closed
nrayburn-tech wants to merge 1 commit intooxc-project:mainfrom
nrayburn-tech:lsp-publish-unknown-rule-messages
Closed

feat(oxc_language_server): Publish a message when there are UnknownRules errors building the LinterBuilder#7087
nrayburn-tech wants to merge 1 commit intooxc-project:mainfrom
nrayburn-tech:lsp-publish-unknown-rule-messages

Conversation

@nrayburn-tech
Copy link
Collaborator

I think this retains the current CLI behavior of exiting on unknown rules (that's still being discussed, but I figured I should just keep it the same here). This modifies the language server to emit a message to editors which then display a notification within the editor.

Ref #6988

@graphite-app
Copy link
Contributor

graphite-app bot commented Nov 2, 2024

Your org has enabled the Graphite merge queue for merging into main

Add the label “0-merge” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “hotfix” to add to the merge queue as a hot fix.

You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link.

@github-actions github-actions bot added A-linter Area - Linter A-cli Area - CLI A-editor Area - Editor and Language Server C-enhancement Category - New feature or request labels Nov 2, 2024
@codspeed-hq
Copy link

codspeed-hq bot commented Nov 2, 2024

CodSpeed Performance Report

Merging #7087 will not alter performance

Comparing nrayburn-tech:lsp-publish-unknown-rule-messages (95a5bf2) with main (79bf74a)

Summary

✅ 30 untouched benchmarks

@nrayburn-tech nrayburn-tech force-pushed the lsp-publish-unknown-rule-messages branch from 32f7bad to 95a5bf2 Compare November 3, 2024 00:57
@nrayburn-tech
Copy link
Collaborator Author

The unknown rules check was pulled out of main for the 0.11 release. This needs to wait until that is re-added.

If it isn’t going to be added back (or added back differently), then this can be closed.

@Boshen Boshen self-assigned this Nov 5, 2024
@nrayburn-tech
Copy link
Collaborator Author

Closing for now since this probably won't be enabled again for a while. #7257

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-cli Area - CLI A-editor Area - Editor and Language Server A-linter Area - Linter C-enhancement Category - New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants