Make Google Drive destination options and folderId optional#125
Merged
Conversation
…ing to My Drive root when omitted
|
🎉 This PR is included in version 1.14.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
1 participant
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.
The delivery pipeline already accepts a
google-drivedestination withoutoptionsand saves the file to the root of My Drive (verified against the live integration). The schema requiredoptions.folderId, rejecting requests the platform handles fine. This relaxes the contract to match actual behaviour and documents the default: nofolderId→ My Drive root, default filename.Verify:
pnpm build && pnpm test:smoke— bundled schema showsrequired: ["provider"]forGoogleDriveDestination; generated Zod accepts{"provider": "google-drive"}.