Closed SimantoR closed 4 years ago
@SimantoR thanks for the detailed description and bug report. This is definitely something we want to fix! It looks like the description parsing logic is barfing on some of the documentation that's associated with EditForm
.
@mkArtakMSFT do you have a good way to move this issue to aspnet/Razor.VSCode or should I just manually do it? Not sure how we're moving issues these days.
Thank you for the quick response @NTaylorMullen. I started building few internal tools with Blazor and would like this bug rooted out as best as possible. I will try to help with my limited abilities. Blazor is amazing and managing states with it is so much easier and better than the previous webapp with razor approach.
One thing I do wanna ask is, is there any plans to support browser APIs through Blazor or do we have to rely heavily on JS for those things (like camera access)?
@SimantoR We provide integration with browser APIs (through Mono) when they overlap with core .NET APIs, like HttpClient. The community has implement a bunch of JS interop libraries for some browser APIs that you can find on NuGet (see https://github.com/AdrienTorris/awesome-blazor#libraries--extensions for a listing). For other browser APIs you will need to write the JS interop code yourself. Mono may also generate API wrappers for the browser APIs at some future point, but that's not something we're shipping yet.
Just FYI @SimantoR, I sent dotnet/aspnetcore-tooling#1545 which should solve this problem going forward. Thanks again for the detailed report!
Describe the bug
A clear and concise description of what the bug is. Intellisense from Razor Language Server fails when using EditForm. Not sure if its for any other type or just custom types like EditForms.
To Reproduce
Steps to reproduce the behavior:
<EditForm></EditForm>
tag.ctrl+space
:<EditForm ${cursor}></EditForm>
Expected behavior
Expected behavior includes autocomplete for things like
OnValidSubmit
andModel
Screenshots
Razor Log: