Restructure incoming JSON and template JSON that goes into CurveBox to handle single or multiple curves, depths, lines, and rectangles.
Have to think about where things need to be explicit, explicit or automatic, and extensible vs. built-in.
Should start to do some testing that will help guide what to do when information is missing now that the input and template data structures are getting kinda complex.
What are things people could put into the templates that make intuitive sense but wouldn't work? How to identify those and return intuitive instructions and error messages?
This isn't something that can be cleared by itself. Likely it will spawn smaller more constrained issues that will be cleared and this will eventually fade away into "not actively being worked" status.
Restructure incoming JSON and template JSON that goes into CurveBox to handle single or multiple curves, depths, lines, and rectangles.
Have to think about where things need to be explicit, explicit or automatic, and extensible vs. built-in.
Should start to do some testing that will help guide what to do when information is missing now that the input and template data structures are getting kinda complex.
What are things people could put into the templates that make intuitive sense but wouldn't work? How to identify those and return intuitive instructions and error messages?
This isn't something that can be cleared by itself. Likely it will spawn smaller more constrained issues that will be cleared and this will eventually fade away into "not actively being worked" status.