What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Added types to align with new-ish data returned by the API
What is the current behavior? (You can also link to an open issue here)
Doesn't account for newly added gifRef
The current implementation assumes a comment is placed directly on the canvas not on a Frame. However a comment can also be placed on a Frame and if so will return a FrameOffset rather than a Vector
What is the new behavior (if this is a feature change)?
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...) Added types to align with new-ish data returned by the API
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Paint.gifRef: string
Comment.client_meta: Vector2 | FrameOffset
Other information: