Skip to content
This repository was archived by the owner on Sep 26, 2024. It is now read-only.

Stop Eating Optional ; after @typeparam#36

Merged
TanayParikh merged 3 commits intomainfrom
taparik/fixTypeparamSemicolon
Jan 21, 2022
Merged

Stop Eating Optional ; after @typeparam#36
TanayParikh merged 3 commits intomainfrom
taparik/fixTypeparamSemicolon

Conversation

@TanayParikh
Copy link
Contributor

@TanayParikh TanayParikh commented Jan 20, 2022

We'd implemented optional ; for @typeparam however by eating the token we were causing issues with the syntax tree. @ryanbrandenburg provided a failing test so implemented this fix accordingly.

Fixes: dotnet/aspnetcore#39616

@TanayParikh TanayParikh marked this pull request as ready for review January 20, 2022 22:08
Copy link
Contributor

@ryanbrandenburg ryanbrandenburg left a comment

Choose a reason for hiding this comment

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

I still don't really understand the cspans files or why all those .mappings.txt's changed, but it seems the the ";" is now included in .stree.txt and the verifier doesn't fail so we know the SyntaxTree length should be correct, so I'm happy.

@TanayParikh TanayParikh merged commit 848e96c into main Jan 21, 2022
@TanayParikh TanayParikh deleted the taparik/fixTypeparamSemicolon branch January 21, 2022 15:11
TanayParikh added a commit that referenced this pull request Jan 25, 2022
* Add Razor Directive Tests

* Stop eating token

* Baseline updates

(cherry picked from commit 848e96c)
TanayParikh added a commit that referenced this pull request Jan 25, 2022
* Add Razor Directive Tests

* Stop eating token

* Baseline updates

(cherry picked from commit 848e96c)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

@typeparam TItem; causes invalid syntax tree due to missing ";"

3 participants

Comments