Task #93901
Updated by Henrik Elsner about 3 years ago
Currently in v10 there are the Default- and the FrontendRestrictionContainer. I'm proposing to introduce the 'BackendRestrictionContainer' or 'DeletedRestrictionContainer' which serves the same purpose as the FrontendRestrictionContainer within their Context. The FE Container does regulate all the start- and endtime fields, while this is often not wanted within the BE. E.g. for APIs or similar all of the data is needed except the deleted. So the only restriction of this container would be the DeletedRestriction. This might seem obsolete as it is very small in its size, but would be helpful as one would not have to create that own container in each project with an API or similar functionalities, also the block of <pre> $this->queryBuilder->getRestrictions()->removeAll(); </pre> could be spared. Especially now with the dependency injection the queryBuilder instance could be created directly with the new container to be already fully setup as needed when using it in the single classes DeletedRestrictionContainer would probably be the better name as the usage would not be limited. I flagged it as feature, but this could be a task too so we could backport it - depending on the overall feedback.