Conversation
…n collections Co-Authored-By: judah@buildwithfern.com <jsklan.development@gmail.com>
Contributor
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
Co-Authored-By: judah@buildwithfern.com <jsklan.development@gmail.com>
…ry params Co-Authored-By: judah@buildwithfern.com <jsklan.development@gmail.com>
tjb9dc
approved these changes
Jan 7, 2026
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.
Description
Optional query parameters in generated Postman collections now appear unchecked by default in the Postman UI. This prevents users from accidentally sending optional parameters they don't intend to use.
Link to Devin run: https://app.devin.ai/sessions/856aff1fcdf64cdf81e4df76bd67dd60
Requested by: @jsklan
Changes Made
disabled: optional<boolean>field to thePostmanUrlVariabletype definition incollection.ymlgetQueryParams()inGeneratedExampleRequest.tsto setdisabled: truefor optional query parametersunrecognizedObjectKeys: "passthrough"option to serialization inwritePostmanCollection.ts(required because the Postman SDK doesn't yet have thedisabledfield in its schema)Implementation Notes
Optionality Detection: The task description suggested using
availability?.required, but this field doesn't exist in the IR types. Instead, I used the standard pattern from other generators:valueType.type === "container" && valueType.container.type === "optional".Serialization Workaround: The
@fern-fern/postman-sdkpackage doesn't have thedisabledfield defined in itsPostmanUrlVariabletype. To preserve the field during serialization, I addedunrecognizedObjectKeys: "passthrough"to thejsonOrThrowcall. This allows the new field to pass through until the SDK is regenerated.Human Review Checklist
valueTypefor optionality is the correct patternpassthroughworkaround - is this acceptable until the SDK is updated?Testing
disabled: trueappears in generated collection.json files for optional parametersBefore:
After: