Closed Tyrrrz closed 1 month ago
Attention: Patch coverage is 0%
with 1 line
in your changes missing coverage. Please review.
Project coverage is 34.88%. Comparing base (
bc4d39a
) to head (0cc90ef
). Report is 1 commits behind head on main.
Files | Patch % | Lines |
---|---|---|
...nConsole/Pages/App/Playground/NewAccount.cshtml.cs | 0.00% | 1 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Without rewriting the razor page, you could just define the page handler as an endpoint, and add the validation on the minimal api endpoint similarly to what we do in the back-end.
Part of PAS-472
Since we're sending the form data using Vue and completely bypassing Razor Pages request pipeline, the validation attributes are not properly honored. I've added validation for Hints in Vue to avoid vague 400 errors on invalid hints. This is hacky, but a proper solution would require rewriting the page to not use Vue to send the registration request, or have better validation infrastructure on our front-end. I don't think it's worth the effort, given other priorities.