Aspnetcore: Component compilation support needs to add diagnostics for markup errors

Created on 2 Jan 2019 · 3Comments · Source: dotnet/aspnetcore

The Blazor compiler adds diagnostics for things like missing end tags, and mismatched start/end tags. We don't have that support yet for the new component compiler.

This should probably done in the IR lowering phase.

Please find a few skipped tests in the aspnet/AspNetCore-Tooling repo that refer to this issue.

Done area-blazor bug

Source

rynowak

All 3 comments

@rynowak General Question about the repo-merge of Blazor into the AspNetCore-Repo: how can one distinct issues related to blazor from all the other ones? (in this case, this one was only found because I knew that you're closely related to Blazor - looking at labels/projects/whatever, I don't see any blazor-specific classifier)
Sorry for being off-topic and thanks for your answer!

DNF-SaS on 2 Jan 2019

Thanks for asking, I think we'll probably end up using a label like area-Components or area-Blazor. Right now it's still the holidays here so the dust hasn't quite settled yet 😆

rynowak on 2 Jan 2019

👍1

You can also look at https://github.com/orgs/aspnet/projects/19 where we're tracking the components productization work

rynowak on 2 Jan 2019

👍1

Was this page helpful?

0 / 5 - 0 ratings