New routes for layer permissions bundle #973
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
LayerPermissionHandler
would be replacement forGetPermissionsLayerHandlers
andSaveLayerPermissionHandler
. AlsoGetAllRolesHandler
can be removed since the newerManageRoles
does basically the same thing.The response from LayerPermissionHandler for GET request would be layers and their permissions for each role (that have permissions):
Where "12", "43" and "23" are role ids corresponding to roles like "Guest" or "User" or "Admin" and the array lists permissions that the role has.
Sending id-parameter with a layer id can be used to get permissions for single layer.