- Issue created by @jonathanshaw
The work in 📌 Replace HostEntity::isEnabledForRegistration Active is a significant change to a key piece of the architecture and an important extension point, so it deserves a minor release. We're still in the process of finalising all the details and ensuring that other systems play nicely with it. These issue discusses which other issues should be addressed before making the next minor release that includes this new validation.
-
📌
RegistrationAccessControlHandler should rely on RegistratonHostEntityHandler to consider the validation for edit access
Active
-
📌
HostEntityInterface should implement CacheableDependencyInterface
Active
-
📌
Refactor UniqueRegistrantConstraintValidator
Active
-
📌
The set_and_forget setting is no longer needed
Active
-
📌
Decide whether 'status' and 'close' validation errors should be shown at same time
Active
-
📌
Consider registration validation performance impact
Active
-
📌
RegistrationIsOpen constraint should add cache expiry metadata
Active
-
📌
Use HostEntity::isAvailableForRegistration in RegisterAccessCheck
Active
-
📌
Refactor registration_waitlist RegistrationValidationEventSubscriber
Active
-
📌
Enhance the admin override checker service
Active
-
📌
Waitlist validation subscriber better as swapped plugin class
Active
Active
3.3
Registration Core