-
Notifications
You must be signed in to change notification settings - Fork 395
[TS] Fix ts-strict errors in Vue components (Part 2) #3123
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
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 for fixing my errors, appreciate it!
| key: item.id || item.name | ||
| })) as (components['schemas']['Node'] & { key: string })[] | ||
| ) | ||
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.
For this, since we only need the key for the purpose of rendering, maybe we can just generate a unique key if the name doesn't exist
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 am going to leave this change to you (in a separate PR) as it involves with larger scale logic change
Co-authored-by: Christian Byrne <[email protected]>
Co-authored-by: Christian Byrne <[email protected]>
Add optional chaining to nodeDef.description access to prevent "Cannot read properties of undefined (reading 'description')" error when node type is not found in nodeDefStore. Follows same pattern as previous fixes in commits: - 290bf52 (Fix frontend node tooltip error #911) - e8997a7 (Fix ts-strict errors in Vue components Part 2 #3123) Fixes CLOUD-FRONTEND-STAGING-1B
Ref: #3120
This PR is part of the bigger effort to enable strict mode in tsconfig.
┆Issue is synchronized with this Notion page by Unito