Skip to content

Conversation

@Afsoon
Copy link
Contributor

@Afsoon Afsoon commented Dec 21, 2025

Related to #4656

Implement warn-todo vitest rule

@Afsoon Afsoon requested a review from camc314 as a code owner December 21, 2025 19:33
@github-actions github-actions bot added A-linter Area - Linter C-enhancement Category - New feature or request labels Dec 21, 2025
@codspeed-hq
Copy link

codspeed-hq bot commented Dec 21, 2025

CodSpeed Performance Report

Merging #17228 will not alter performance

Comparing Afsoon:vitest-warn-todo (3a908e7) with main (c8c5341)

Summary

✅ 4 untouched
⏩ 41 skipped1

Footnotes

  1. 41 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports.

Copy link
Contributor

@connorshea connorshea left a comment

Choose a reason for hiding this comment

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

Documentation suggestions :)

@connorshea connorshea changed the title feat(linter/eslint-plugin-vitest): Implemented warn todo eslin rule feat(linter/eslint-plugin-vitest): Implemented vitest/warn-todo rule Dec 21, 2025
@github-actions github-actions bot added the A-cli Area - CLI label Dec 22, 2025
@camc314 camc314 self-assigned this Dec 22, 2025
Comment on lines 55 to 62
fn run_once(&self, ctx: &LintContext) {
let mut possibles_jest_nodes = collect_possible_jest_call_node(ctx);
possibles_jest_nodes.sort_unstable_by_key(|n| n.node.id());

for possible_jest_node in &possibles_jest_nodes {
WarnTodo::run(possible_jest_node, ctx);
}
}
Copy link
Contributor

Choose a reason for hiding this comment

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

we can use run_on_jest_node rather than manually collecting the calls here

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated to use run_on_jest_node

@Afsoon Afsoon force-pushed the vitest-warn-todo branch 2 times, most recently from 99936dd to 922b59d Compare December 23, 2025 15:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-cli Area - CLI A-linter Area - Linter C-enhancement Category - New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants