Repository navigation
Fix existing DriveUsers.create singleton request envelope - #64
Merged
Merged
Conversation
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.
Existing DriveUsers.create request-envelope correction
Send ordinary dictionaries without an
objectskey directly as the documented singleton POST /driveusers/ request. Explicit objects wrappers and list/tuple inputs continue through the unchanged base implementation. Existing signature, query forwarding and response decoding remain unchanged; other resource create methods are unaffected.This deliberately changes ordinary-dictionary wire bytes. It does not establish that the server rejects legacy wrapped alternatives, nor certify those alternatives as public contracts. GET/list/delete evidence gaps and full-operation closure remain open.
Exactly three files: resource override, six finite offline regression tests, and CI expected count 222→228. Dependencies and workflows unchanged. Independent SAFE review binds patch
1ba7eccaca6e9b9d5eea1b54f060ae436b800efe5d4eaf628f677ccbc82a31da, base38aa6a707faa279461e9f60f04503836e9a2768e, tree366db617dc47882a883638e83d98236957923eb7.Retained native source evidence: focused six tests and finite228 passed. Baseline failures are executor-recorded same-checkout pristine-production evidence; no separate immutable full baseline manifest was retained. This is not independently observed baseline custody or provider rejection evidence. Installed-wheel hosted Python3.10/3.11/3.12 checks on this actual head are required before landing.
No live RDS/cloud operation, release, deployment, acceptance discovery or whole-family/portfolio closure claim.