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

chore(linter) convert catch error name to a warning #1700

Merged

Conversation

camc314
Copy link
Collaborator

@camc314 camc314 commented Dec 16, 2023

No description provided.

Copy link
Collaborator Author

camc314 commented Dec 16, 2023

@github-actions github-actions bot added the A-linter Area - Linter label Dec 16, 2023
Copy link
Collaborator Author

camc314 commented Dec 16, 2023

Merge activity

  • Dec 16, 12:47 PM: @@camc314 started a stack merge that includes this pull request via Graphite.
  • Dec 16, 12:48 PM: Graphite rebased this pull request as part of a merge.
  • Dec 16, 12:52 PM: @@camc314 merged this pull request with Graphite.

Base automatically changed from c/12-16-fix_linter_improve_diagnostic_for_no_useless_spread to main December 16, 2023 17:47
@camc314 camc314 force-pushed the c/12-16-chore_linter_convert_catch_error_name_to_a_warning branch from 655787c to 6c3d402 Compare December 16, 2023 17:48
@camc314 camc314 merged commit f4f0bdf into main Dec 16, 2023
15 checks passed
@camc314 camc314 deleted the c/12-16-chore_linter_convert_catch_error_name_to_a_warning branch December 16, 2023 17:52
Copy link

codspeed-hq bot commented Dec 16, 2023

CodSpeed Performance Report

Merging #1700 will improve performances by 5.2%

Comparing c/12-16-chore_linter_convert_catch_error_name_to_a_warning (6c3d402) with main (c61ea76)

Summary

⚡ 1 improvements
✅ 19 untouched benchmarks

Benchmarks breakdown

Benchmark main c/12-16-chore_linter_convert_catch_error_name_to_a_warning Change
semantic[vue.js] 80.4 ms 76.4 ms +5.2%

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

Successfully merging this pull request may close these issues.

2 participants