Matthieu Riegler
Matthieu Riegler
That looks to be a bug in how we generate the error page. That's not a runtime error but a compiler error. Probably an issue introduced by #59355.
Can you file an issue for that. On Angular.io we had a distinction between both type of errors. https://v17.angular.io/errors
Can you have a look at the failing tests ? Some expect to match the exact error message. Also the lint check expects a body message of 20+ characters.
Can you please rebase on main, it should fix the remaining broken test.
This change requires a cleanup on our side in Google's code base for us to be able to land it. We'll do it in due time aligned with our priorities.
As expected this will require a g3 cleanup and is a breaking change. We'll have to wait for the next breaking change window.
This is a tricky question and I think I see where you're coming from. Angular actually supports/uses both stage 2 and 3. The Stage 2 (aka experimental decorators) are required...
Same answer as for #64493. Validator shouldn't be driven by the UI. Also in your case it looks like you want to implement a custom control that would handle that...
> Please revert the changes in reference and tools/cli We still have a change in `tools/cli`
Looks like we still have an issue. Edit: fixed it myself.