Implement client for default permission endpoints #146
Labels
priority: medium
Medium priority
type: feature
New feature or request
type: maintenance
Related to general repository maintenance
workload: days
Likely takes days to resolve
Milestone
Currently, we have kept the default permission endpoints as fixed paths. Instead, we should probably focus on adding a client for the default API, and for that, we know the routes. Users might still be able to reuse that client if they host a /permissions API at the expected base path (if all they are doing is modifying the behavior of the default endpoints). And if they wanna add a completely different API, then they would also need to implement the client along with it.
Hence, we need to implement a client for the default permission endpoints, which then can be used in the controller logic of a FOCA app.
The text was updated successfully, but these errors were encountered: