Originally created by @mprasil on GitHub (May 19, 2018).
The function doesn't work for UserOrganization with access_all, for Admin or Owner that doesn't have direct CollectionUser mapping.
This is because we only use Collection::find_by_uuid_and_user() in the handler, but the above users don't necessarily need to have access allowed for specific Collection as they can generally access any Collection within Organization. We need to check whether that isn't the case before returning error.
Originally created by @mprasil on GitHub (May 19, 2018).
The function doesn't work for `UserOrganization` with `access_all`, for `Admin` or `Owner` that doesn't have direct `CollectionUser` mapping.
This is because we only use `Collection::find_by_uuid_and_user()` in the handler, but the above users don't necessarily need to have access allowed for specific `Collection` as they can generally access any `Collection` within `Organization`. We need to check whether that isn't the case before returning error.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @mprasil on GitHub (May 19, 2018).
The function doesn't work for
UserOrganizationwithaccess_all, forAdminorOwnerthat doesn't have directCollectionUsermapping.This is because we only use
Collection::find_by_uuid_and_user()in the handler, but the above users don't necessarily need to have access allowed for specificCollectionas they can generally access anyCollectionwithinOrganization. We need to check whether that isn't the case before returning error.@dani-garcia commented on GitHub (May 21, 2018):
This should be fixed by your PR #28 so I'm closing it. Thanks!