-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
[Hot Reload] Source Generator Based Error Breaks Hot Reload #36825
Comments
Is this a known issue @NTaylorMullen or should I create a separate issue for the missing VSCode diagnostic? |
Not a known issue that I know of at least. Sounds like SourceGenerator errors aren't being propagated to the IDE in VSCode? Probably an omnisharp-roslyn thing if I had to guess |
That's a regular compiler error, no? Does it appear when you do |
Error shows up in the error pane (under generated C# file), which explains why the squiggle isn't there for the .razor file. Do we need to remap? |
@chsienki this looks like a source generator caching bug. We were able to workaround this by configuring the Do you happen to know if there was any recent changes made here that might have regressed this? |
This definitively means you're using a pre-RC1 version of the compiler. As a part of fixing the caching bug we ripped that option out of the compiler entirely. It was flipped into an opt-in option. Hence if that is fixing the behavior then you're using a compiler that does not have the fix. |
Closing as this is now fixed plus it's (was) a compiler issue |
Screen.Recording.2021-09-21.at.8.09.03.PM.mov
Repro:
Start with:
This doesn't give any error in VSCode, but it does give the source generator error:
However, even after removing the offending
<input>
tag entirely the source generator error persists (perhaps it should've been marked as a rude edit?). Must exitdotnet watch
and restart to resume functionality.The text was updated successfully, but these errors were encountered: