Standa Lukeš
Standa Lukeš
When compilation has errors an error page that shows only the first error is displayed. It should display all error and warnings on the page, it would help with investigation...
Large route tables can be surprisingly costy :(. It can especialy hurt if you are loading lot of resources not handled by dotvvm and all the routes have to fail...
Sometimes size of JS does not matter and we want to have nicer errors in tracking tools. We should have an easy to use option that will load debug builds...
We should add few extension methods which will validate a specified object using FluentValidation validators and put the errors into our ModelState.
`style` and `script` tags have special treatment in HTML - they contain verbatim text, not any nested elements. We should parse the contents as an unencoded text, simply looking for...
There is a number of problems with these special values: - [ ] They are serialized as string in Newtonsoft.Json, we should add support to coercer for parsing NaN. Seems...
Since controls got shorter and easier to write, it would make sense to allow nested class to be controls. At least in tests it would be quite useful. ```csharp class...
As of v1.1 we have nice cache-friendly content serving mechanism - it should be possible to use images (video, audio and other content) as proposed in the PR #271. Maybe...
We could add a mechanism to collect runtime warnings from DotVVM and display them in the browser console (so the dev can actually read it). On ASP.NET Core, these warnings...
The DotVVM error page now only displays the one error that caused the page to fail. We can certainly improve it to display: * warnings on the page (in yellow...