Replace console.error with friendly error system

[shashank-iitbhu]

Increasing Access

Many functions inside src/webgl and lib/addons currently uses console.error to report errors. It would be more user-friendly and consistent with the p5.js environment to replace these calls with the friendly error system (FES).

Most appropriate sub-area of p5.js?

• Accessibility
• Color
• Core/Environment/Rendering
• Data
• DOM
• Events
• Image
• IO
• Math
• Typography
• Utilities
• WebGL
• Build Process
• Unit Testing
• Internalization
• Friendly Errors
• Other (specify if possible)

Feature enhancement details

For example, take parseASCIISTL function in webgl/loading.js,
I have triggered an error condition and the results,



with console.error:




with FES:

It would be more user-friendly and consistent with the p5.js environment to replace these calls with the friendly error system (FES).

[welcome]

Welcome! 👋 Thanks for opening your first issue here! And to ensure the community is able to respond to your issue, please make sure to fill out the inputs in the issue forms. Thank you!

[shashank-iitbhu]

related PRs and Issues: #6098 and #5649 .

[shashank-iitbhu]

@davepagurek if you can review this. I am willing to work on this issue. Please assign.

[ranjanmangla1]

can I get to work on this issue? this will be my first contribution in processing community

[omsharma29]

where to find this issue I forked the code base in local system??

[samrudh3125]

Do we also have to change the throw new error keywords or only the console.error

[samrudh3125]

@shashank-iitbhu please accept the pull request

[vaishnavi192]

@davepagurek Hey I would like to work on this issue. Can you assign me?

[perminder-17]

Thanks for opening this issue. However, that's not exactly how it works. For example, when I use console.err(e), it means I’m unsure of what’s happening or what kind of error might be occurring, and we get a line from the p5.js library. Friendly errors, on the other hand, are designed to be more helpful to the user. They point out the specific line in your code where the issue happened and even suggest possible solutions. These errors are not only formatted clearly but also provide guidance. You can see an example below where both an error message and a friendly error message are shown.

And also, when we are using console.error(maybe your error message) in your sketch, it probably mean we need to show it in an error format.

So, I need to close this issue.