Repository navigation
Conversation
HEAD /elements/{uuid} answered a single element with a 200 or a 403. The
new GET /elements/permission takes a list of element uuids and returns the
ones the user has the given right on, so a client resolving several
elements no longer needs one call per element.
Signed-off-by: Florent MILLOT <75525996+flomillot@users.noreply.github.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
The endpoint returns elements, not a permission, which its name now reflects, along with the path it calls on directory-server. The controller parameter is renamed permissionType, as the service it delegates to already named it, and the operation and response descriptions are reworded accordingly. Signed-off-by: Florent MILLOT <75525996+flomillot@users.noreply.github.com>
…rmissions Signed-off-by: Florent MILLOT <florent.millot_externe@rte-france.com>
|
|
Closing: the permissions on shared modifications are no longer resolved by the front-end, so this endpoint has no consumer left. network-modification-server now asks directory-server itself, through gridsuite/directory-server#267, which answers the permission held on each element. |
3 participants
Depends on gridsuite/directory-server#267.
HEAD /explore/elements/{uuid}?permission=…answers a single element with a 200 or a 403, so a client resolving several elements needs one call per element.It is replaced by
GET /explore/elements/accessible?ids=…&accessType=…, which returns the uuids the user has the given right on, the forbidden and the unknown ones being left out. It delegates to the directory-server endpoint added in the PR above.