-
Notifications
You must be signed in to change notification settings - Fork 116
Collection/Project imports change request Id, breaking request-chaining #103
Comments
hi Granger; good catch!; I'm releasing a major release soon (which will make everything file-system-centric) and I will include the fix in the new version |
Perfect. This is most important issue for everyone who wants own synchonizer/exporter. Preserving original IDs during import (or other solution) causes that exported file will be same as imported. Current behaviour duplicates workspace or requests (depend of import type) so it is useless. |
@archywillhe Any ETA for this new major release ? |
@Totalus Will be somewhere in feb; sorry for the delay - there're more things to fix than expected (and then suddenly I got too hectic with my other work in the recent months) |
Hi! |
Expected Behavior
This is a copy of the original bug that came over with the Kong code: Kong/insomnia#5942
It starts out talking about "tags", but in the comments, things change to talking about request-chaning. There's a chance it's fixed in this PR: Kong/insomnia#6521
There's a comment that implies this got fixed over in Kong/insomnia#5983 but the bug still exists in Insomnium 0.2.3-a: https://github.com/ArchGPT/insomnium/releases/tag/core%400.2.3-a .
Import of a collection/project exported in v4 Json or Yaml (from Insomnia or Insomnium) will retain the exported request Ids, like it does all of the other Ids, so request chaining works.
Actual Behavior
The requests in each collection each get a newly generated request Id. Since the request-chaining setups reference the original Id (from the Json/Yaml export file), all of that functionality breaks.
Reproduction Steps
Is there an existing issue for this?
Additional Information
No response
Insomnium Version
0.2.3-a
What operating system are you using?
macOS
Operating System Version
Ventura 13.6.2 (22G320)
Installation method
The .dmg download file
Last Known Working Insomnium version
none
The text was updated successfully, but these errors were encountered: