processing / processing/p5.js

[p5.js 2.0+ Bug Report]: FES warning for mismatched vector sizes doesn't show the line where the issue occurred, and has spelling errors

Open Beginner friendly
#8,835 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

p5.js 2.0+
Dominant language
JavaScript
Stars
24k
Forks
3.8k
Avg merge
3d 16h
Merged PRs (30d)
25

Description

Most appropriate sub-area of p5.js?
  • Accessibility
  • Color
  • Core/Environment/Rendering
  • Data
  • DOM
  • Events
  • Image
  • IO
  • Math
  • Typography
  • Utilities
  • WebGL
  • WebGPU
  • p5.strands
  • Build process
  • Unit testing
  • Internationalization
  • Friendly errors
  • Other (specify if possible)
p5.js version

2.3.0.rc-6

Web browser and version

Brave 1.90.122

Operating system

Linux Mint 22.1

Steps to reproduce this
Snippet:

function setup() {
  let v = createVector(1,2);
  let w = createVector(1,2,3);
  v.add(w);
  print(v.toString());
}


The output is:

When working with two vectors of different sizes, the smaller dimension is used. In this operation, both vector will be treated as 2D vectors, and any additional values of the linger vector will be ignored. 
vector[2, 4] 

It doesn't include the number of the line that caused the issue (line 4 here), and there are two spelling errors: "both vector" should be "both vectors", and "the linger vector" should be "the longer vector"

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

Run the supplied p5.js sketch with mismatched 2D and 3D vectors and inspect the Friendly Errors handling for the resulting warning. Trace how the warning is generated and how the source line is reported. Done means the warning identifies the triggering line and corrects “both vector” and “linger vector” to the reported wording.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
developer-experience
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.