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
I should be able to download p5's sketch without any error.
The sketch actually does export successfully, using the saved version of the project.
We are getting this message because we make a PUT request to the API before exporting a sketch. That API request will fail if the user is not the owner of the sketch. The easiest solution would be to only make that API call if there is a logged in user and that user is the owner of the sketch.
There is some nuance here with regards to how we would handle local/unsaved changes. Right now those changes would not be applied if it is not your sketch. This is part of a larger discussion happening in #2904.
I haven't looked into the issue yet but why are we calling autoSaveProject before downloading? It doesn't seem necessary to save someone's project before downloading it i think so. Removing that step should fix it.
p5.js version
No response
What is your operating system?
None
Web browser and version
No response
Actual Behavior
Expected Behavior
I should be able to download p5's sketch without any error.
The sketch actually does export successfully, using the saved version of the project.
We are getting this message because we make a PUT request to the API before exporting a sketch. That API request will fail if the user is not the owner of the sketch. The easiest solution would be to only make that API call if there is a logged in user and that user is the owner of the sketch.
The relevant code is here:
p5.js-web-editor/client/modules/IDE/hooks/useSketchActions.js
Lines 42 to 45 in 64c36ca
There is some nuance here with regards to how we would handle local/unsaved changes. Right now those changes would not be applied if it is not your sketch. This is part of a larger discussion happening in #2904.
Steps to reproduce
Steps:
The text was updated successfully, but these errors were encountered: