EasyCorp / EasyCorp/EasyAdminBundle
Autocomplete permission
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 4.3k
- Forks
- 1.1k
- Avg merge
- 8d 2h
- Merged PRs (30d)
- 11
Description
The permissions required to access autocomplete are the same as those required to access the index. There should be a dedicated permission for autocomplete.
// not a typo; we intentionally reuse the INDEX action for permission checks in autocomplete
if (!$this->isGranted(Permission::EA_EXECUTE_ACTION, ['action' => Action::INDEX, 'entity' => null, 'entityFqcn' => $context->getEntity()->getFqcn()])) {
throw new ForbiddenActionException($context);
}
Example:
User 1 is allowed to administer the entity (and therefore has access to the index).
User 2 should be allowed to use the entity through autocomplete without being able to access the index.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the shown autocomplete permission check and compare it with the existing index permission handling. Identify where these permissions are defined and exercised; done means autocomplete can be granted independently while index access remains restricted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, symfony
- Domain
- authorization, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100