Conversation
ksen0
approved these changes
Mar 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related to processing/p5.js-website#1240. Part of the problem there was that some inline code in the reference was manually unescaped in the p5 source code, while others were not. This led to us having to try to figure out which to escape or which not to. It's probably easier for everyone if it's consistent: never manually escape in docs.
This was generated by:
find src -name "*.js" | xargs perl -p -i -e 's/</</g'find src -name "*.js" | xargs perl -p -i -e 's/>/>/g'escapeHelperthat maps raw symbols to escaped versionsnpm run custom:dev https://github.com/processing/p5.js.git#unescapeChanges:
<and>in the docs are replaced by<and>Screenshots of the change:
PR Checklist
npm run lintpasses