VcClusterComputeResource type dilemma #299
Replies: 8 comments 2 replies
-
Hey @unbreakabl3 it should, yes... actually quite a lot of classes need to be changed to being classes. Writing a task for that now |
Beta Was this translation helpful? Give feedback.
-
Hi @unbreakabl3 @Michaelpalacce I just noticed this is still open. Did we update the code or it is still a pending issue? |
Beta Was this translation helpful? Give feedback.
-
@unbreakabl3 no worries, just checking the status. Is it only changing from interface to class? Maybe I can try to close it before the current release happens? |
Beta Was this translation helpful? Give feedback.
-
Yes, it should be just a change from interface to class. |
Beta Was this translation helpful? Give feedback.
-
Moved to an issue, I am currently working to close it, hopefully today. |
Beta Was this translation helpful? Give feedback.
-
Hi @VenelinBakalov, |
Beta Was this translation helpful? Give feedback.
-
if it is for vCenter plugin no need, I added them all to the PR, if it is for other plugins, let's add separate issues for each plugin |
Beta Was this translation helpful? Give feedback.
-
Hi all.
In vRO API, the "VcClusterComputeResource" is an Interface (in vRBT as well). But technically, it is a class. And it's acting as a class. Because it has an instance, once initialized/returned from vCenter. In JS, of course, this error doesn't exist. In my example, @ts-ignore solves the problem, and everything works once it is transpiled. Should the "VcClusterComputeResource" be a class in vRBT?
@Michaelpalacce , @joroaf - may you guys know?
Beta Was this translation helpful? Give feedback.
All reactions