Skip to content

fix(postman): emit empty arrays in sample request bodies - #702

Merged
pasoevi merged 1 commit into
mainfrom
pasoevi/postman-array-examples
Oct 6, 2026
Merged

pasoevi merged 1 commit into
mainfrom
pasoevi/postman-array-examples

Conversation

@pasoevi

@pasoevi pasoevi commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

Why?

Importing the Postman collection and pressing Send on Conversations → Reply returned a 500. The sample body sent an empty string for attachment_urls, but the API reads that field as a list, so the collection failed out of the box for anyone trying the endpoint.

How?

Sample generation now emits an empty list for array fields instead of falling back to an empty string, and a missing form-body serializer that had been silently breaking Preview collection generation since April is restored.

Generated with Claude Code

The sample body for Conversations -> Reply shipped "attachment_urls": "",
which the API iterates as an array and returns a 500 for, so importing the
collection and pressing Send failed out of the box.

Example#value had no branch for an array of primitives, so those fields fell
through to the '' fallback. Collection#serialize was called by both the
urlencoded and formdata paths but never defined, which broke Preview
generation entirely once a multipart endpoint was added - the committed
Preview collection had not been regenerated since April as a result.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@pasoevi
pasoevi requested review from a team and MarkHarrison03 and removed request for a team October 6, 2026 08:30
@pasoevi
pasoevi merged commit 9b6da0d into main Oct 6, 2026
4 checks passed
@pasoevi
pasoevi deleted the pasoevi/postman-array-examples branch October 6, 2026 08:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants