-
-
Notifications
You must be signed in to change notification settings - Fork 35.5k
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
Nodes: export viewport and minor fixes #26698
Conversation
Can you please also add BumpMapNode, HashNode, and Schlick_to_F0? They were added in previous PRs but weren't, I think, added to the exports. |
super( scope ); | ||
|
||
} | ||
|
||
construct( builder ) { |
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.
Hmm... Would it make sense to rename construct()
to build()
?
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.
I think build
is already used for the last step -- turning the node into a shader code fragment. The construct
name for the node constructing step seems nice 👍
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.
Ah, maybe setup()
then? Or configure()
?
Just trying to differentiate it from constructor()
...
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.
setup()
is interesting.
As title.