-
Notifications
You must be signed in to change notification settings - Fork 8
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
[INT] Fixed pkg not building with 2.0.0 #74
Conversation
eva-vashkevich
commented
Jul 24, 2024
- Changed how components are defined which was causing "RangeError: Maximum call stack size exceeded" error on pkg-build
- Changed id for cluster class cards to handle duplicate names
export default (Vue as VueConstructor< | ||
Vue & InstanceType<typeof CreateEditView> | ||
>).extend({ | ||
export default { |
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.
Can this use defineComponent instead? I believe we lose some vue component typing with a plain export default
in components
@@ -307,7 +304,7 @@ export default (Vue as VueConstructor< | |||
}); | |||
}, | |||
clickedType(obj: {[key:string]: any}) { | |||
this.clusterClassObj = this.clusterClasses.find((x: ClusterClass) => x.metadata.name === obj.id); | |||
this.clusterClassObj = this.clusterClasses.find((x: ClusterClass) => x.metadata.uid === obj.id); |
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.
When I try to run yarn build-pkg capi
this line throws an error because uid
is not defined in the ClusterClass
interface.
Is there a reason to rely on metadata.uid
instead of id
here? The latter would be more consistent with dashboard code generally
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.
lgtm
5815761
to
a451c6b
Compare