Skip to content

Document type coercion for Postman imports #49

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mintlify wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Document type coercion for Postman imports #49

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion converters/postman-to-bruno.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,4 +66,10 @@ sidebarTitle: "Postman to Bruno"
);
```
</Tab>
</Tabs>
</Tabs>

## Type coercion

The converter automatically handles non-string values that may appear in Postman collections. Numeric and boolean values in headers, query parameters, path parameters, form body fields, and authentication fields are coerced to strings during conversion. Null or undefined values default to empty strings (or appropriate fallback values for auth fields).

Postman collections may also store headers in non-standard formats such as concatenated strings (`"Content-Type: application/json\r\nAccept: */*"`) or mixed arrays of strings and objects. The converter normalizes all header formats into consistent key-value pairs.
4 changes: 4 additions & 0 deletions get-started/import-export-data/postman-migration.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -108,5 +108,9 @@
</Info>

<Info>
Postman allows variable values to be numbers, booleans, or objects, but Bruno stores all variable values as strings. During import, non-string values are automatically converted — for example, `5000` becomes `"5000"`, `true` becomes `"true"`, and objects are serialized as JSON strings.

Check warning on line 111 in get-started/import-export-data/postman-migration.mdx

View check run for this annotation

Mintlify / Mintlify Validation (bruno-a6972042) - vale-spellcheck

get-started/import-export-data/postman-migration.mdx#L111 

Did you really mean 'booleans'?
</Info>

<Info>
Bruno also converts non-string values in collection data during import. Numeric or boolean values in headers, query parameters, path parameters, form body fields, and authentication fields are automatically coerced to strings. Additionally, Postman collections that use concatenated string headers (e.g., `"Content-Type: application/json\r\nAccept: */*"`) or mixed header formats are normalized into standard key-value pairs.
</Info>
Loading