Add JSON file for PVector#setHeading()
Resolves #620 by adding the JSON file for PVector#setHeading() generated using the instruction at https://github.com/processing/processing-website?tab=readme-ov-file#keywordstxt.
Deploy Preview for java-processing-faf822 ready!
| Name | Link |
|---|---|
| Latest commit | 8018e7ea3c2874837e9761dac064a9b3310201f5 |
| Latest deploy log | https://app.netlify.com/sites/java-processing-faf822/deploys/67e3c0db16697b00085ed848 |
| Deploy Preview | https://deploy-preview-621--java-processing-faf822.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Looks like the deploy preview is missing setHeading(), is anything still missing?
Edit: how do I see all pages that are generated? ...59 more pages
Hi @babaissarkar
The .json files should be generated by the Doclet script:
https://github.com/processing/processing-doclet/blob/main/README.md
The instructions are a bit outdated (still mentioning Ant) but the overall process should work to generate the .json files.
Note: The fact that it requires cloning multiple repos next to each other on your local machine, running a script, and pushing the changes is a holdover from the old days of the project and not a recommended practice in general. We'll have to automate this with GitHub actions at some point.
The
.jsonfiles should be generated by the Doclet script:
I generated them with the Doclet script, but forgot to add PVector.json and the updated one for PVector#heading().
Note: The fact that it requires cloning multiple repos next to each other on your local machine, running a script, and pushing the changes is a holdover from the old days of the project and not a recommended practice in general. We'll have to automate this with GitHub actions at some point.
I agree, this should be automated.
Merged. Thanks for your patience! ✨