Show previous messages
November 10, 2019 at 10:53am
I never encountered such problem
I don't see anything that could overwrite completely the settings/environments
I'll do a manual export when ready just to be sure
it's a very basic json file
If it was one Linux / macOS it could have been linked to hardened binaries for notarization (or signing for Snap store)
but on Windows i have no clue what have happened
December 5, 2019 at 6:24pm
unfortunately there is no easy way to do this. Exports are "locked" for each version. This system is quite old, and I am rewriting the whole import / export system. It will be released very soon in a v1.7.0. Also, the "wiped" environments is a known bug that has been corrected (https://github.com/mockoon/mockoon/issues/217). But normally it should affect only new installation, not existing ones. So I am not sure what happened in your case and nothing like this has been reported yet.
Concerning making the export compatible with 1.6.0, it's not an easy task. Because imported environment are not migrated to new data format. and some things changed since v1.4.0. The idea would be to change the version of the file to 1.6.0, add what is missing on the data (reproducing what migration.lib.ts does, starting at migration number 6 (multiple route responses))., then calculate a checksum of the data like
wrapExportmethod does in data.service.ts
I know it's a hassle and I am really sorry. This system has been develop at the very beginning of Mockoon and I realize now that it is completely unusable.
v1.7.0 is my top priority and will be out in some days. I will try to make it compatible with older exports (by auto migrating the data, not checking the version or the checksum anymore, etc)