-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Import Bruno Collection fails - ValidationError: headers are required #2583
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.
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
Comments
+1 similar scenario occurring for me on Ubuntu. I have a more complex collection but still see the same error that @sigiswald is seeing as well. |
+1 confirmed same scenario / bug; seen both on:
In both cases using Bruno v1.20.2 with:
|
I've found a workaround (based on seeing the PR in #2598). When the bug is seen, manually edit the export JSON before attempting to import again. Such that there is at least an empty array on the
For the example scenario in this report, this workaround allowed me to import the "test.json" Bruno collection. It also worked for me (using Bruno v1.20.2) in a more complex Bruno collection exported on Windows and imported in Linux (after applying this workaround). |
Nice! That seems like it would satisfy the current |
Thank you @sfreeman422 and @mdxs !!! Your analysis, feedback and certainly the PR is much appreciated! |
…usebruno#2583 (usebruno#2598) * Removed headers key on folderRootSchema as it seems unlikely that headers are actually required here * Removed launch.json * Added back package-locks * reverted package-lock * removed only the .required
I have checked the following:
Describe the bug
Bruno v1.20.2 (and also v1.20.1) on Windows.
test.json
Exporting/importing as a Postman collection works fine.
Kind regards,
/Sigiswald
.bru file to reproduce the bug
No response
Screenshots/Live demo link
The text was updated successfully, but these errors were encountered: