- 🇬🇧United Kingdom catch
I'm bumping this down to normal - Symfony has given us no other options here, except possibly 📌 Discuss whether to decouple from Symfony Validator Active , but it is mostly annoyance having to suppress those messages.
The "Symfony\Component\Validator\Context\ExecutionContextInterface::setNode()" method is considered internal Used by the validator engine. Should not be called by user code. It may change without further notice. You should not extend it from "Drupal\Core\TypedData\Validation\ExecutionContext".
The "Symfony\Component\Validator\Context\ExecutionContextInterface::setGroup()" method is considered internal Used by the validator engine. Should not be called by user code. It may change without further notice. You should not extend it from "Drupal\Core\TypedData\Validation\ExecutionContext".
The "Symfony\Component\Validator\Context\ExecutionContextInterface::setConstraint()" method is considered internal Used by the validator engine. Should not be called by user code. It may change without further notice. You should not extend it from "Drupal\Core\TypedData\Validation\ExecutionContext".
The "Symfony\Component\Validator\Context\ExecutionContextInterface::markConstraintAsValidated()" method is considered internal Used by the validator engine. Should not be called by user code. It may change without further notice. You should not extend it from "Drupal\Core\TypedData\Validation\ExecutionContext".
The "Symfony\Component\Validator\Context\ExecutionContextInterface::isConstraintValidated()" method is considered internal Used by the validator engine. Should not be called by user code. It may change without further notice. You should not extend it from "Drupal\Core\TypedData\Validation\ExecutionContext".
The "Symfony\Component\Validator\Context\ExecutionContextInterface::markGroupAsValidated()" method is considered internal Used by the validator engine. Should not be called by user code. It may change without further notice. You should not extend it from "Drupal\Core\TypedData\Validation\ExecutionContext".
The "Symfony\Component\Validator\Context\ExecutionContextInterface::isGroupValidated()" method is considered internal Used by the validator engine. Should not be called by user code. It may change without further notice. You should not extend it from "Drupal\Core\TypedData\Validation\ExecutionContext".
The "Symfony\Component\Validator\Context\ExecutionContextInterface::markObjectAsInitialized()" method is considered internal Used by the validator engine. Should not be called by user code. It may change without further notice. You should not extend it from "Drupal\Core\TypedData\Validation\ExecutionContext".
The "Symfony\Component\Validator\Context\ExecutionContextInterface::isObjectInitialized()" method is considered internal Used by the validator engine. Should not be called by user code. It may change without further notice. You should not extend it from "Drupal\Core\TypedData\Validation\ExecutionContext".
We cannot just remove the methods, because we are implementing the interface. Maybe we can in D10.0.
Active
10.1 ✨
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I'm bumping this down to normal - Symfony has given us no other options here, except possibly 📌 Discuss whether to decouple from Symfony Validator Active , but it is mostly annoyance having to suppress those messages.