-
Notifications
You must be signed in to change notification settings - Fork 2
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
Curvedpath fix #101
Curvedpath fix #101
Conversation
@@ -26,15 +26,18 @@ export interface CurvedPathEdgeData { | |||
control: number | number[]; | |||
sourceColor?: GraferInputColor, | |||
targetColor?: GraferInputColor, | |||
pickingColor?: number | [number, number, number, number]; |
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 presume vectors are used quite a bit, so in that case it may be useful to extract this into a type at least the array. i.e type vec4 = { r: number, g: number .... }
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.
vectors are used quite a bit, this vec4/uvec4 is present in a few places in the code, i think if we want to consolidate the types it might be better to do it in a seperate PR so we dont have 4 additional unrelated files in this PR. what do you think?
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'm fine with that, this was just a thought but yes if we have this throughout the code base we should have a clean up PR
No description provided.