-
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
feat: Typescript 5/4 #72
Conversation
@@ -81,7 +72,7 @@ export type Operation = | |||
* @param {Object} data Entity data to use for creation | |||
* @return {Object} API operation | |||
*/ | |||
export function createOperation(type: string, data: any): CreateOperation { | |||
export function create(type: string, data: any): CreateOperation { |
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.
Even though they probably are not ment to be used outside this project, must we not wait with changing function names until it's time to make a major version release?
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.
they were not exposed publicly from index.ts, so only way to have used them would be if someone imported them directly from @ftrack/api/dist/operation
, which I don't think is supported behavior. The function names reflect their names in the now removed default 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.
I think I'm just overly cautious.
Changes
Additional fixes and enhancements from trying out the beta.
Test