Skip to content

test(linter/lsp): implement tests for oxlint.config.ts support#18827

Closed
camc314 wants to merge 1 commit intomainfrom
c/02-02-test_linter_lsp_implement_tests_for_oxlint.config.ts_support
Closed

test(linter/lsp): implement tests for oxlint.config.ts support#18827
camc314 wants to merge 1 commit intomainfrom
c/02-02-test_linter_lsp_implement_tests_for_oxlint.config.ts_support

Conversation

@camc314
Copy link
Contributor

@camc314 camc314 commented Feb 2, 2026

No description provided.

@github-actions github-actions bot added A-editor Area - Editor and Language Server C-test Category - Testing. Code is missing test cases, or a PR is adding them labels Feb 2, 2026
Copy link
Contributor Author

camc314 commented Feb 2, 2026

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more


How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • 0-merge - adds this PR to the back of the merge queue
  • hotfix - for urgent hot fixes, skip the queue and merge this PR next

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

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

@camc314 camc314 changed the base branch from c/02-02-feat_linter_lsp_implement_support_for_oxlint.config.ts to graphite-base/18827 February 2, 2026 01:36
@camc314 camc314 force-pushed the c/02-02-test_linter_lsp_implement_tests_for_oxlint.config.ts_support branch from b728c53 to 744b302 Compare February 2, 2026 01:36
@camc314 camc314 changed the base branch from graphite-base/18827 to c/02-02-feat_linter_vscode_run_extension_when_js_configs_are_detected February 2, 2026 01:36
@graphite-app graphite-app bot changed the base branch from c/02-02-feat_linter_vscode_run_extension_when_js_configs_are_detected to graphite-base/18827 February 2, 2026 09:05
@camc314 camc314 force-pushed the graphite-base/18827 branch from a8f6bbb to 75a56d8 Compare February 2, 2026 09:10
@camc314 camc314 force-pushed the c/02-02-test_linter_lsp_implement_tests_for_oxlint.config.ts_support branch from 744b302 to 6990b90 Compare February 2, 2026 09:10
@camc314 camc314 changed the base branch from graphite-base/18827 to c/02-02-feat_linter_vscode_run_extension_when_js_configs_are_detected February 2, 2026 09:10
@camc314 camc314 force-pushed the c/02-02-feat_linter_vscode_run_extension_when_js_configs_are_detected branch from 75a56d8 to e973c79 Compare February 2, 2026 09:10
@graphite-app graphite-app bot changed the base branch from c/02-02-feat_linter_vscode_run_extension_when_js_configs_are_detected to graphite-base/18827 February 2, 2026 09:17
@graphite-app graphite-app bot force-pushed the c/02-02-test_linter_lsp_implement_tests_for_oxlint.config.ts_support branch from 6990b90 to 446d18c Compare February 2, 2026 09:23
@graphite-app graphite-app bot force-pushed the graphite-base/18827 branch from 75a56d8 to 1753209 Compare February 2, 2026 09:23
@graphite-app graphite-app bot changed the base branch from graphite-base/18827 to main February 2, 2026 09:24
@graphite-app graphite-app bot force-pushed the c/02-02-test_linter_lsp_implement_tests_for_oxlint.config.ts_support branch from 446d18c to 8723c60 Compare February 2, 2026 09:24
Copy link
Member

Choose a reason for hiding this comment

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

"ts_config" is not a nice name. We have oxc.tsConfigPath which could be confused.

Copy link
Member

@Sysix Sysix left a comment

Choose a reason for hiding this comment

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

I started an LSP test stack here: #18827
I would more prefer to create own LSP tests there, instead of more integration tests with the linter. My plan is to reduce them to a minimum

@camc314
Copy link
Contributor Author

camc314 commented Feb 2, 2026

I started an LSP test stack here: #18827
I would more prefer to create own LSP tests there, instead of more integration tests with the linter. My plan is to reduce them to a minimum

sounds good, we can close this one?

@camc314 camc314 closed this Feb 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-editor Area - Editor and Language Server C-test Category - Testing. Code is missing test cases, or a PR is adding them

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants