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
fix #5942: Retain exported ID for resource #6521
base: develop
Are you sure you want to change the base?
Conversation
It would be nice if this MR is prioritized! Export of request chains has been pretty broken for a while now. |
When is this being released? seems like a simple fix to me |
My team is experiencing the same problem. If you export a document, then import later, existing requests are assigned new request IDs. Every Tag, Request Chaining, basically everywhere you've made a reference to a request's ID is now broken. Steps to reproduce:
This occurs for Insomnia 8.4.0 on both PC and Mac |
Bump - any updates on when this might be released? |
I just switched to postman again.. |
By debugging a little, you can see that each request has a unique and global id. Wouldn't it be better for each request to be unique in its document? With these corrections, it is possible to import requests with their ID'S, however. If you already have these ID'S in your insomina it returns an error. I'm trying to research more about requests and documents within the code. |
|
1 similar comment
|
Is there any update on this PR? When it is going to be available? |
Closes #5942
If an imported config has references to requests via the response plugin they are dereferenced as the imported config gets all new ids.
If this has downstream consequences, please let me know.
changelog(Fixes): Added a fix to retain the id from imported resources