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
On Windows using the executable on the release page for version 1.5.3, when clicking the "Get started by creating a completely new, empty threat model" or "Explore a sample model" option, an error message is shown saying that it cannot find module ../../ThreatDragonModels/new-model/new-model.json
You can still create a new model by navigating to File > New
This was graciously reported by our friend Simon.
Expected behaviour
A new model is created when clicking either option
Environment
Version: 1.5.3
Platform: Desktop App
OS: Windows (unknown version)
To Reproduce
Click "Get started by creating a completely new, empty threat model." OR "Explore a sample model. This is a good option if you are new to Threat Dragon"
An error is displayed
This seems to not affect the Linux snapcraft distribution. I did not see this behavior when testing on MacOS with the signed/notarized release either, though it may be worth another check in case I missed something.
The text was updated successfully, but these errors were encountered:
Ah, I know what has caused this and the fix is not too hard. Wish I had caught this before version 1.5.3 - all to do with consolidating the file set and shuffling files around , but then making sure it is cross-platform.
@lreading shall I take this on? I have a fix in mind
Describe the bug
On Windows using the executable on the release page for version 1.5.3, when clicking the "Get started by creating a completely new, empty threat model" or "Explore a sample model" option, an error message is shown saying that it cannot find module
../../ThreatDragonModels/new-model/new-model.json
You can still create a new model by navigating to File > New
This was graciously reported by our friend Simon.
Expected behaviour
A new model is created when clicking either option
Environment
To Reproduce
This seems to not affect the Linux snapcraft distribution. I did not see this behavior when testing on MacOS with the signed/notarized release either, though it may be worth another check in case I missed something.
The text was updated successfully, but these errors were encountered: