-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
added loadFilterShader function #7445
base: dev-2.0
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, your updates look great! Just one tiny change I noticed in the formatting of the example code and then I think we're good to go.
* @param {Function} [failureCallback] callback to be called if there is an error | ||
* loading the shader. Will be passed the | ||
* error event. | ||
* @return {Promise<p5.Shader>} a promise that resolves with a shader object |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good @Rishab87 !
@limzykenneth we probably need to update the docs for other load*
methods to indicate they return promises now if we haven't already, and likely we will need to update the FES code to handle templated Promise types
Co-authored-by: Dave Pagurek <[email protected]>
fixed the formatting |
@davepagurek do tell if anything else needs to be done |
Resolves #6852
Changes:
I have added loadFilterShader function to keep things consistent as mentioned in the issue.
Screenshots of the change:
PR Checklist
npm run lint
passes