You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Accessing the validator service from the TestContainer triggers a deprecation while it should still be allowed.
How to reproduce
Create a test that accesses the validator service from the TestContainer.
This triggers a deprecation that accessing validator from the container is deprecated and DI should be used instead. But TestContainer is precisely meant to allow allow accessing private services.
The issue is that validator has the tag container.private which would add it in the test service locator, but it is decorated by debug.validator (the TraceableValidator), which looses that condition. And so the validator id is not added in the private test locator.
However, as this wanna-be-private is now handled with tags, I'm not sure we actually have a way to mark an alias as becoming private in the future.