[p5.js 2.0+ Bug Report]: Typo in Spanish reference documentation for ellipseMode()
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 95/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
Research direction
Open the Spanish ellipseMode() reference at https://p5js.org/es/reference/p5/ellipseMode/ and locate the paragraph for the CORNERS mode. Correct the copied reference from ellipseMode(CORNER) to ellipseMode(CORNERS), then reload the page and verify the Spanish text matches the expected wording.
Written by the indexing model from the issue text.
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
Latest (2.0+)
Web browser and version
All ( But I'm on FireFox )
Operating system
All ( But I'm on MacOSX )
Steps to reproduce this
Steps:
- Go to the Spanish reference for ellipseMode: https://p5js.org/es/reference/p5/ellipseMode/
- Read the paragraph corresponding to the
CORNERSmode. - Notice that it incorrectly mentions
ellipseMode(CORNER)instead ofellipseMode(CORNERS).
Snippet:
There is a typo/copy-paste error in the Spanish translation text.
- Actual Text: "ellipseMode(CORNER) utiliza los dos primeros parámetros como la ubicación de una esquina del cuadro delimitador de la elipse. Los siguientes parámetros son la ubicación de la esquina opuesta."
- Expected Text: "ellipseMode(CORNERS) utiliza los dos primeros parámetros como la ubicación de una esquina del cuadro delimitador de la elipse. Los siguientes parámetros son la ubicación de la esquina opuesta."
- Dominant language
- JavaScript
- Stars
- 24.1k
- Forks
- 3.8k
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 34
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from processing/p5.js
-
[p5.js 2.0+ Bug Report]: ReferenceError: p5 is not defined when calling loadPixels/get/copy/mask on p5.MediaElement in ESMPossibly taken @Pcmhacker-piro claimed this 6 days ago. OpenArea:Core Area:DOM
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
processing/p5.js#9189 · 1 comment ·
Maintainers usually reply within 2 days
-
[Bug]: p5.Image.prototype.copy and blend do not scale destination coordinates for high pixel densityPossibly taken @Pcmhacker-piro claimed this 22 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
processing/p5.js#9169 ·
Maintainers usually reply within 2 days
-
[p5.js 2.0+ Bug Report]: int() truncates numbers to 32 bits, disagreeing with the same value passed as a stringPossibly taken @rajanpanth claimed this 4 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
processing/p5.js#9129 · 3 comments · 1 assignee ·
Maintainers usually reply within 2 days
-
[p5.js 2.0+ Bug Report]: splitTokens() returns [] for a caret delimiter and throws for a backslashOpen
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
processing/p5.js#9126 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
processing/p5.js#9125 · 1 comment ·
Maintainers usually reply within 2 days
All issues in processing/p5.js
Similar issues
-
sendDefaultPii is reported as deprecated on ReactNativeOptions although dataCollection is hiddenOpenBug React-Native Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
getsentry/sentry-react-native#6830 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
szTheory/exifcleaner#383 ·
Maintainers usually reply within 1 day
-
Frontend good first issue P2-medium UI UX
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Deepak3699/Ai_Mentor#179 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
DrozmotiX/ioBroker.tado#1213 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
python-visualization/folium#2293 · 1 comment ·
Maintainers usually reply within 1 day