-
Notifications
You must be signed in to change notification settings - Fork 172
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[Instrument] Remove exception from NDB_BVL_Instrument::factory #8290
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
driusan
added
Cleanup
PR or issue introducing/requiring at least one clean-up operation
php
Pull requests that update Php code
labels
Dec 20, 2022
driusan
force-pushed
the
InstrumentSeparateAccessCheck
branch
from
December 20, 2022 14:53
be27b1f
to
783e387
Compare
This was referenced Dec 20, 2022
driusan
added
the
Blocking
PR should be prioritized because it is blocking the progress of another task
label
Dec 21, 2022
driusan
force-pushed
the
InstrumentSeparateAccessCheck
branch
from
February 15, 2023 18:52
783e387
to
473bfea
Compare
ridz1208
reviewed
Feb 21, 2023
@@ -252,6 +252,11 @@ class Unresolved extends Endpoint implements ETagCalculator | |||
'', | |||
true | |||
); | |||
if ($instrument->_hasAccess($user) == false) { | |||
return new \LORIS\Http\Response\JSON\NotFound( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not Found?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
This removes the exception from NDB_BVL_Instrument::factory(), so that it's possible to call hasAccess on an instrument. Currently the hasAccess or Factory call mix concerns, making it difficult for a module to check if a user has access to an instrument.
driusan
force-pushed
the
InstrumentSeparateAccessCheck
branch
from
February 21, 2023 19:12
473bfea
to
a4784be
Compare
ridz1208
reviewed
Feb 21, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one last comment
ridz1208
reviewed
Feb 21, 2023
ridz1208
approved these changes
Feb 21, 2023
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
This removes the exception from NDB_BVL_Instrument::factory(), so that it's possible to call hasAccess on an instrument. Currently the hasAccess or Factory call mix concerns, making it difficult for a module to check if a user has access to an instrument.