Skip to content

fix(parser): parsing errors occur when type parameters are followed by as or satisfies#9553

Merged
graphite-app[bot] merged 1 commit intomainfrom
03-05-fix_parser_parsing_errors_occur_when_type_parameters_are_followed_by_as_or_satisfies
Mar 5, 2025
Merged

fix(parser): parsing errors occur when type parameters are followed by as or satisfies#9553
graphite-app[bot] merged 1 commit intomainfrom
03-05-fix_parser_parsing_errors_occur_when_type_parameters_are_followed_by_as_or_satisfies

Conversation

@Dunqing
Copy link
Member

@Dunqing Dunqing commented Mar 5, 2025

close: #9541

Copy link
Member Author

Dunqing commented Mar 5, 2025


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.

@github-actions github-actions bot added A-parser Area - Parser C-bug Category - Bug labels Mar 5, 2025
@codspeed-hq
Copy link

codspeed-hq bot commented Mar 5, 2025

CodSpeed Performance Report

Merging #9553 will not alter performance

Comparing 03-05-fix_parser_parsing_errors_occur_when_type_parameters_are_followed_by_as_or_satisfies (a88eb56) with main (2f08b16)

Summary

✅ 39 untouched benchmarks

@Boshen Boshen marked this pull request as draft March 5, 2025 02:59
@Dunqing Dunqing force-pushed the 03-05-fix_parser_parsing_errors_occur_when_type_parameters_are_followed_by_as_or_satisfies branch from 667c981 to c902b25 Compare March 5, 2025 03:43
@Dunqing Dunqing requested a review from Boshen March 5, 2025 03:51
@Dunqing Dunqing force-pushed the 03-05-fix_parser_parsing_errors_occur_when_type_parameters_are_followed_by_as_or_satisfies branch from c902b25 to aa3319e Compare March 5, 2025 05:36
@Dunqing Dunqing marked this pull request as ready for review March 5, 2025 05:57
@Boshen Boshen added the 0-merge Merge with Graphite Merge Queue label Mar 5, 2025
Copy link
Member

Boshen commented Mar 5, 2025

Merge activity

  • Mar 5, 1:08 AM EST: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
  • Mar 5, 1:08 AM EST: A user added this pull request to the Graphite merge queue.
  • Mar 5, 1:14 AM EST: A user merged this pull request with the Graphite merge queue.

@graphite-app graphite-app bot force-pushed the 03-05-fix_parser_parsing_errors_occur_when_type_parameters_are_followed_by_as_or_satisfies branch from aa3319e to a88eb56 Compare March 5, 2025 06:09
@graphite-app graphite-app bot merged commit a88eb56 into main Mar 5, 2025
33 checks passed
@graphite-app graphite-app bot deleted the 03-05-fix_parser_parsing_errors_occur_when_type_parameters_are_followed_by_as_or_satisfies branch March 5, 2025 06:14
@oxc-bot oxc-bot mentioned this pull request Mar 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

0-merge Merge with Graphite Merge Queue A-parser Area - Parser C-bug Category - Bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

linter: TS(17000), parsing errors on valid TS syntax

2 participants