processing / processing/processing4

Feature request: Friendly Error System for Processing

Open
#1,365 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

paused
Dominant language
Java
Stars
494
Forks
183
Avg merge
4h 39m
Merged PRs (30d)
3

Description

Relevant sub-area for this feature?

Other (specify if possible)

Feature details
Feature description

During Google Summer of Code 2023, a Friendly Error Messages system for Processing (inspired by the p5.js Friendly Error System) was developed by Will Rabalais (@WillRabalais04) with mentorship by Sam Pottinger (@sampottinger). This work adds clearer, contextual error messages, documentation links, and debugger improvements.

However, this work was never included in Processing and is not available to users today.

This request is to review, update if needed, and include this work in a future Processing release.

Note: This is meant to document work completed during GSoC 2023 and to put a pin in it for future consideration. It does not signal urgency, assign responsibility, or presume the level of effort required. The goal is mainly to ensure this work is visible and not lost.

Benefits
  • Improves error messages that are currently cryptic and hard to understand
  • Helps beginners debug and learn more effectively
  • Brings Processing closer to p5.js in terms of learning-centered tooling
Challenges
  • Updating the 2023 code to match the current Processing codebase and UI system (Compose)
  • Expanding test coverage and checking language server compatibility
Additional context
Screenshots
Image Image
Would you like to help implement this feature?

No, I’m just suggesting the feature

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the original PR 771 and the GSoC 2023 project report to understand the existing Friendly Error Messages implementation. Then compare it with the current Processing codebase and Compose UI, including its test and language-server needs. Done means an updated, reviewed system is integrated into a future Processing release with expanded coverage and compatible debugger behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.