menu

Mockoon

Mockoon's official community. Get help, discuss new features.

Channels
Chat
view-forward
# All channels
view-forward
# General
view-forward
# Announcements
view-forward
# Bugs
view-forward
# Features
view-forward
# Help
view-forward
Team
Show previous messages

November 10, 2019 at 10:56am
weird :-(
  • reply
  • like
yes :(
  • reply
  • like
I'm recreating them
  • reply
  • like
I'll do a manual export when ready just to be sure
  • reply
  • like
if you reproduce this bug somehow and have an idea how it happened please let me know
  • reply
  • like
it should suffice if I copied the environment.json i assume?
  • reply
  • like
will do
  • reply
  • like
yeah normally
  • reply
  • like
it's a very basic json file
  • reply
  • like
yeah
  • reply
  • like
thanks
  • reply
  • like
and this system didn't change since the beginning of Mockoon
  • reply
  • like
If it was one Linux / macOS it could have been linked to hardened binaries for notarization (or signing for Snap store)
  • reply
  • like
but on Windows i have no clue what have happened
  • reply
  • like

December 5, 2019 at 6:24pm
Anybody know how to convert a saved environment from version 1.4.0 to version 1.6.0? After upgrading Mockoon, no environments are setup. I did an export of the environments before I ran the upgrade.
  • reply
  • like
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 wrapExport method does in data.service.ts
  • reply
  • like
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.
  • reply
  • like
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)
  • reply
  • like

January 20, 2020 at 2:43pm
Hi. Found Mockoon today and thought that it is exactly what I needed. Tested it with my proccess and ran into the same issue: https://github.com/mockoon/mockoon/issues/229 This is very annoying bug which makes it imposible for me to use Mockoon. I wish you could fix it very soon. Thank you!
Edited
  • reply
  • like

January 20, 2020 at 8:49pm
Hi , I tested and indeed got a weird JSON parse error on Mockoon's side when calling an automatically built endpoint (even with proxy mode disabled). But I am not sure if this is the same bug as the one described in the issue. Could you please post here or on the issue (better) a way to reproduce it step by step with sample data if possible. Thank you!
  • reply
  • like

January 24, 2020 at 11:56am
Hi! I uploaded a video to this isssue which shows the problem. Can I help with anything else?
  • reply
  • like
I saw, thank you! I just didn't have time to work on Mockoon the last days. I will try to have a look this weekend.
  • reply
  • like
Thank you!
  • reply
  • like

February 4, 2020 at 1:32pm
Hi there, shall I open a feature request for this ? What do you think ?

Using Rules to test against JSON empty arrays

thumbsup
0
message-simple
5
  • reply
  • like

February 4, 2020 at 8:29pm
of course you can :)
  • reply
  • like
Show more messages