You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Skipped folding range test tracked by #10859
Skipped rename test tracked by #10856
Updated semantic tokens test tracked by #10857
Update folding range tests tracked by #10860
Update spell checking test tracked by #10863
Skipped formatting tests tracked by #10864
Skipped auto insert tests tracked by #10865
@jaredpar Yep, I mentioned this one previously. We've been fixing these on an ad-hoc basis but it turns out it's an issue with any @ directive that razor parses directly.
I plan to fix that holistically rather than doing more one at a time patches, but we're getting into the long tail of what users actually see so not considering this a blocker for fuse rollout right now.
(Aside, apologies I guess I didn't put these issues into milestones but have already triaged them).
Not sure if this is a tooling issue, or difference in results from Roslyn caused by a runtime/designtime compilation difference.
Example differences:
From:
f929020?diff=unified&w=0#diff-a1706b971c83e9c0c358e3db52e305ad63a07dc5a88c23d2ae265ce9e06eaf54L30
I think this is a bad user experience as, in the example above, the closing
div
tag would end up displayed on the same line as the@if
when collapsed.The text was updated successfully, but these errors were encountered: