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

feat(linter/tree-shaking): support try-catch and AwaitExpression #2902

Merged

Conversation

mysteryven
Copy link
Contributor

No description provided.

Copy link
Contributor Author

mysteryven commented Apr 6, 2024

@mysteryven mysteryven changed the title feat(tree-shaking): support try-catch and AwaitExpression feat(linter/tree-shaking): support try-catch and AwaitExpression Apr 6, 2024
@github-actions github-actions bot added the A-linter Area - Linter label Apr 6, 2024
Copy link
Member

Boshen commented Apr 6, 2024

Merge activity

  • Apr 6, 1:58 AM EDT: @Boshen started a stack merge that includes this pull request via Graphite.
  • Apr 6, 1:59 AM EDT: Graphite rebased this pull request as part of a merge.
  • Apr 6, 2:02 AM EDT: @Boshen merged this pull request with Graphite.

Base automatically changed from 04-06-feat_linter/tree-shaking_check_this_in_different_environment to main April 6, 2024 05:58
@Boshen Boshen force-pushed the 04-06-feat_tree-shaking_support_try-catch_and_AwaitExpression branch from 5d2f1f7 to 95fd055 Compare April 6, 2024 05:59
@Boshen Boshen merged commit b053d54 into main Apr 6, 2024
32 checks passed
@Boshen Boshen deleted the 04-06-feat_tree-shaking_support_try-catch_and_AwaitExpression branch April 6, 2024 06:02
Copy link

codspeed-hq bot commented Apr 6, 2024

CodSpeed Performance Report

Merging #2902 will not alter performance

Comparing 04-06-feat_tree-shaking_support_try-catch_and_AwaitExpression (95fd055) with main (acb6eb2)

Summary

✅ 36 untouched benchmarks

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