Fix bulk permissions request body field names - #150
Draft
oshchyhol wants to merge 2 commits into
Draft
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
Motivation
permissions.bulkPermissionsUpdatesends a request body the API does not understand:resourceType/accessLevelare sent camelCase instead of theresource_type/access_levelwire names, and_destroyis built frompermission._destroy(not part of the typed params) while the typeddestroyfield is ignored, so destroy requests are silently dropped. Rails strong params drop the unknown camelCase keys server-side, so the method could not create, update, or destroy any permission.Changes
resourceId/resourceType/accessLevelparams to theresource_id/resource_type/access_levelwire names expected byPUT .../permissions/bulk_destroyfrom the typeddestroyparam; remove the@ts-ignorethat was hiding the bugdestroyasbooleanto match the OpenAPI_destroy: booleancontract (wasstring; a string"false"would still destroy the permission server-side, a booleanfalseis safely ignored)How to test
permissions.bulkPermissionsUpdate(accessId, [{ resourceId, resourceType: "account", accessLevel: "viewer" }])– the permission is actually created/updated with viewer access (previously the API received unknown camelCase keys and rejected the update)destroy: true– the permission is destroyed (previously the_destroyflag never reached the API)destroy: false– the permission is created/updated, not destroyedpermissions.getResources()– unchangedCompanion PRs
Caveat:
destroychanges fromstringtobooleaninPermissionResourceParams. Since_destroynever reached the API before this fix, no caller can depend on the old string behavior.