-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Closed as duplicate of#1120
Description
Most appropriate sub-area of p5.js?
- Accessibility
- Color
- Core/Environment/Rendering
- Data
- DOM
- Events
- Image
- IO
- Math
- Typography
- Utilities
- p5.strands
- WebGL
- DevOps, Build process, Unit testing
- Internationalization (i18n)
- Friendly Errors
- Other (specify if possible)
p5.js version
Both 1.0 and 2.0
Web browser and version
N/A
Operating system
N/A
Steps to reproduce this
Steps:
- Go to https://p5js.org/reference/p5/createVector/ (or https://beta.p5js.org/reference/p5/createvector/ for 2.0).
- Scroll down to the "Returns" section at the bottom of the page.
- Click on the link that says "p5.Vector: new p5.Vector object."

- Observe that it does not go to https://p5js.org/reference/p5/p5.Vector/, but rather https://p5js.org/reference/p5/createVector/#/p5.Vector.
Notes:
I believe this is the line causing this issue:
Line 37 in 28b17b5
| * @return {p5.Vector} new <a href="#/p5.Vector">p5.Vector</a> object. |
The link #/p5.Vector is wrong, though other parts of the documentation were able to use it and still go to the correct page. My guess is that this has something to do with how the docs are built?
Reactions are currently unavailable