Dave Pagurek
Dave Pagurek
That's a really good catch! I had forgotten that those primitives don't go through the existing `Shape` class. I think the `Shape` stuff I was talking about will still be...
Thanks @madhav2348 ! Let me know if you run into any issues in the process.
Hi @madhav2348, what version of node are you using? [We were seeing some issues like this before](https://github.com/processing/p5.js/pull/7644), but only on node 18 and under. Could you try 20 or higher...
Also I think you probably don't need to update browser_errors.js and file_errors.js, we're using zod in src/core/friendly_errors/param_validator.js here: https://github.com/processing/p5.js/blob/d51184b5598e4d51dca12905aeb3387b2e6a95bf/src/core/friendly_errors/param_validator.js#L6 After upgrading the zod version via `npm upgrade zod@^3.25.0`, what happens...
Thanks @kajal-jotwani! I'll assign this to you.
Sorry for the delay, I ended up leaving a similar comment on the PR. but for continuity here: I think we want to still document the properties in the section...
Looks like in https://github.com/processing/p5.js/pull/7135 a check was added for shapes that go off of the max end of the canvas. Probably a similar PR is needed to add an additional...
Sorry for the delay @eyaler, sounds good!
@digitaldina I think that works too! Wrapping the whole thing in a `try`/`catch` could prevent *any* error from escaping, but also runs the risk of us missing important bugs, so...
@eyaler that makes sense to me!