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
{{ message }}
This repository has been archived by the owner on Sep 10, 2021. It is now read-only.
Platform
How were you accessing the qri frontend?
[ ] app.qri.io
[ ] electron app
[ x] dev webapp
Version
What version of the Qri frontend are you using?
0.8.2
Describe the bug
Running dry run doesn't actually save any coding progress. The only way to save is to hit the save button. This then boots me out of the entire environment. Then I would have to delete both the body and the structure to continue working. The only way to dodge this pain point is to code my entire transform in one shot. Instead of just working out a piece of the transform, saving my progress, and continuing what I was working on.
To Reproduce
Steps to reproduce the behavior:
Try to write part of a script, save it and continue working.
Expected behavior
I expected to hit save, it saves my transform script, and continue working. I think it would be good to have a "Run" button. A Dry Run is a fake run. Save would save the current status of the files and Run would save everything and create the dataset.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Platform
How were you accessing the qri frontend?
[ ] app.qri.io
[ ] electron app
[ x] dev webapp
Version
What version of the Qri frontend are you using?
0.8.2
Describe the bug
Running dry run doesn't actually save any coding progress. The only way to save is to hit the save button. This then boots me out of the entire environment. Then I would have to delete both the body and the structure to continue working. The only way to dodge this pain point is to code my entire transform in one shot. Instead of just working out a piece of the transform, saving my progress, and continuing what I was working on.
To Reproduce
Steps to reproduce the behavior:
Try to write part of a script, save it and continue working.
Expected behavior
I expected to hit save, it saves my transform script, and continue working. I think it would be good to have a "Run" button. A Dry Run is a fake run. Save would save the current status of the files and Run would save everything and create the dataset.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: