Change Details

Currently the `WikibaseEntityPermissionChecker` class relies on `WikiPageEntityStorePermissionChecker` in order to determine users have correct permissions to create or edit entities. However, this class is not quite fit for purpose in our REST API use-cases, as it deals with many other user messaging concerns apart from checking permission for editing and creating entities. Namely, the methods of the class we use return a generic `Status` object which discards helpful interfaces and information that inherently exist in the `PermissionStatus` objects it deals with. For the sake of clearly separating concerns, and decoupling the REST API interface logic form the rest of the Wikibase interfaces (Wiki Pages, Action API, etc.). This task proposes that we create our own class for dealing with permission logic. **Acceptance Criteria**: -[ ] `WikibaseEntityPermissionChecker` no longer relies on `WikiPageEntityStorePermissionChecker`

Currently the `WikibaseEntityPermissionChecker` class relies on `WikiPageEntityStorePermissionChecker` in order to determine users have correct permissions to create or edit entities. However, this class is not quite fit for purpose in our REST API use-cases, as it deals with many other user messaging concerns apart from checking permission for editing and creating entities. Namely, the methods of the class we use return a generic `Status` object which discards helpful interfaces and information that inherently exist in the `PermissionStatus` objects it deals with. For the sake of clearly separating concerns, and decoupling the REST API interface logic form the rest of the Wikibase interfaces (Wiki Pages, Action API, etc.). **Acceptance Criteria**: [] Handling the permission checks in Wikibase logic no longer relies on inspecting the specific messages used in status objects

Currently the `WikibaseEntityPermissionChecker` class relies on `WikiPageEntityStorePermissionChecker` in order to determine users have correct permissions to create or edit entities. However, this class is not quite fit for purpose in our REST API use-cases, as it deals with many other user messaging concerns apart from checking permission for editing and creating entities. Namely, the methods of the class we use return a generic `Status` object which discards helpful interfaces and information that inherently exist in the `PermissionStatus` objects it deals with. For the sake of clearly separating concerns, and decoupling the REST API interface logic form the rest of the Wikibase interfaces (Wiki Pages, Action API, etc.). This task proposes that we create our own class for dealing with permission logic. **Acceptance Criteria**: -[ ] `WikibaseEntityP [] Handling the permissionChecker` checks in Wikibase logic no longer relies on `WikiPageEntityStorePermissionChecker`inspecting the specific messages used in status objects