You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When a domain story is exported multiple times, the sequence of the JSON nodes in the .egn file is different every time. This has no effect on the functionality of Egon (ie, importing still works fine and semantically, the stories are the same). But users who put their .egn files in a sourcecode repository like Git will have a hard time to see actual changes in their files.
This seems to happen only in Firefox, not Chrome.
To Reproduce
[If applicable, attach a .dst file. ]
Steps to reproduce the behavior:
Go to '...'
Click on '....'
Click on '....'
See error
Expected behavior
Only JSON nodes that have actually changed should be different from the previous .egn file.
Exporting the same Domain Story twice should result in the exact same .egn file.
Version
Egon: v2.1.0
Browser: Firefox
OS: Windows
The text was updated successfully, but these errors were encountered:
Describe the bug
When a domain story is exported multiple times, the sequence of the JSON nodes in the .egn file is different every time. This has no effect on the functionality of Egon (ie, importing still works fine and semantically, the stories are the same). But users who put their .egn files in a sourcecode repository like Git will have a hard time to see actual changes in their files.
This seems to happen only in Firefox, not Chrome.
To Reproduce
[If applicable, attach a .dst file. ]
Steps to reproduce the behavior:
Expected behavior
Version
The text was updated successfully, but these errors were encountered: