fix(studio): export via server with project assets - #680
Merged
Conversation
Header STL/STEP still used the legacy in-browser worker (no async wrap, no lib.fromSTEP), and Export POSTed bare source so production looked for /tmp/<step>. Route all Studio exports through /__kernelcad/export and send projectSlug+source on /p/<slug> so the server materializes complementary STEP.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Header STL/STEP used the legacy worker (
new Functionwithout async → await errors). Export also POSTed bare source, so production resolvedlib.fromSTEP('./2.0u_blank_costar.stp')to/tmp/...and failed for 3MF/STL.Changes
exportViaServer()for Header + Export tab/p/<slug>, POSTprojectSlug+sourceso the API materializes STEP assetsTest plan