fix(membership): Ensure membership is in current organization when revoking #2658
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.
Context
Today it is possible the revoke a membership from any organization as long as you know the ID.
The
Mutations::Memberships::Revoke
is delegating the logic toMemberships::RevokeService
, but this service is not checking that the membership is part of any organization (Membership.find_by
)Description
This PR refactors the service to use the common
call
pattern.It also update the mutation to require an Organization and lookup for the membership with a scope to the current organization.