Repository navigation
Conversation
|
Needs test. |
|
Looks as if we won't implement this, at least not in this way. close? |
|
I vote we leave it open / in draft until an alternative implementation presents itself. Is there a reason you want to close this? |
No reason. I think we decided it's best implemented as a specific query. |
|
We need to do more investigative work for #561. Let's keep this in draft for now. We can circle back once the 3.0.0 milestone is complete. |
A query is done to determine the highest permission level the given user (or group) has on the target collection/data_object. A specific query will be used if the calling user has the availability, otherwise a reasonably efficient general query is used instead.
|
Hm. Looks like I force-pushed over the old branch. Note for the future, don't do that. (Look for pre-existence of the branch name in GitHub. Duh.) Well, luckily I am very confident of the new code being better.... |
|
Will mark ready for review once I've run the tests through with rudra's changes included |
Check if the
usernamed (may be a user or group) has privilege at or above the givenaccess_levelto the collection or data object named bypath