- Issue created by @penyaskito
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
It seems we did this in the original
_entity_accessissue: #1947432: Add a generic EntityAccessCheck to replace entity_page_access() → .Why did we not do it for the "create" variant? 🤔
_entity_access allows dynamic entity types. Looking at the docblock from EntityAccessCheck:
* example.route:
* path: '/foo/{entity_type}/{example}'
* requirements:
* _entity_access: 'example.delete'
* options:
* parameters:
* example:
* type: entity:{entity_type}
_entity_create_access (EntityCreateAccessCheck), however, only uses parameters for bundles, but it would be useful to allow dynamic entity types too.
This came up in Experience Builder, 📌 Add access control for "code components" and "asset libraries", special case: instantiated code components must be accessible to *all* Active
Allow dynamic entity types in EntityCreateAccessCheck
Active
11.0 🔥
entity system
It seems we did this in the original _entity_access issue:
#1947432: Add a generic EntityAccessCheck to replace entity_page_access() →
.
Why did we not do it for the "create" variant? 🤔