* Switched to Miniconda image
* Update cad endpoint url
and some minor tweaks
Co-authored-by: Jeremy Wright <wrightjmf@gmail.com>
Co-authored-by: Jeremy Wright <wrightjmf@gmail.com>
* Rough changes to make the CadQuery integration work with the customizer
* Tweak runCQ
* Switched to Anaconda
* Cleaned up code
* Update CadHub after anaconda
Related to #547
* Add final tweaks to CQ customizer
* Separated out customizer.json from params.json
* Changes after discussing CadHub integration
* linting runCQ
Co-authored-by: Kurt Hutten <k.hutten@protonmail.ch>
* Update menuConfig.tsx
* Revert "Update menuConfig.tsx"
This reverts commit 7be28e2a76.
* second attempt
* Update mosaic tree to remove and add the console.
* Added Toggle UI component
* Remove console noise from Toggle component
Co-authored-by: Kurt Hutten <k.hutten@protonmail.ch>
Co-authored-by: Frank Johnson <frankjohnson1993@gmail.com>
If there's an error in netlify's prerendering service,
we don't have access to the log so we have to spin it up locally to
check.
textures was causing a issue on the home page resulting in "Fatal Error"
as the social preview text, not good.
As a bonus I thing I fix FE sentry logging too.
* Only send customizer params when it's open
* Add customizer reset button and have two modes of customizer vs not
depending of if the customizer is open.
* Remove re-render on customizer open/close in project profile
The jscad worker code was hosted as a static asset, making it odd
javascript where we have to be conscious of what javascript features we
can use and if it will work on older browsers, plus it can't be
typescript like the rest of the codebase.
Since redwood 0.36 we using webpack 5 should make loading workers easy
https://webpack.js.org/guides/web-workers/
But I had trouble with this (see:
https://community.redwoodjs.com/t/has-anyone-tried-workers-with-webpack-5-rw0-36-x/2394)
and instead used the webpack 4 loader without any issues
This issue relates to #411 , and is a checklist item on #444Resolves#494
