Rename conflicting sphere() functions to avoid shadowing p5.js built-in #896
Conversation
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
|
@perminder-17 Thank you so much for reviewing and merging this PR! |
Thanks to you for working on this one. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description:
This PR resolves a naming conflict in the
intro-to-p5-strandstutorial page. A custom helper function namedsphere()was shadowing the built-in p5.jssphere()function, causing confusion. This renames two user-defined functions namedsphere()torandomPositionOnSphere()andgetAnimatedSpherePosition()Verification:
sphere()torandomPositionOnSphere()andgetAnimatedSpherePosition()does not affect functionality.sphere()function name.Issue: Closes #868