Remco Post
Remco Post
I found that workflow-subscriptions cannot be the only thing in a package. If you have something else (I added a property definition I believe) you can pull the package.
> @pe1pip we've been able to successfully push stuff into vRO in vRA8 using a profile that looks like the one below... > @cars My particular issue is with embedded...
> Hi @pe1pip & @yattong, can you validate if this profile configuration fit your needs and solve your issue? > > > ``` > > > > multitenancy > >...
Hi, I think it is.
Hi Guys, sorry for responding so slowly... I just did a few tests and can confirm that this is still an issue with 2.37. Basically, cfg el mocking is broken...
I think my PR has been merged, meaning that this issue is now resolved.
This would be nice... we're working towards improving our unit testing by leveraging yest, and the newer TSC could help
would be nice if somebody could look at this
the problem arises if you want additional properties in the Error object, in this case the `cause` property: ```ts export class NsxtError extends Error { public readonly cause: ErrorCause constructor...
This is a well documented 'feature' of typescript, see for example: https://stackoverflow.com/questions/41102060/typescript-extending-error-class and https://github.com/microsoft/TypeScript-wiki/blob/7adbad944469a2943c1ba2032a1fb1735b89a8f3/Breaking-Changes.md#extending-built-ins-like-error-array-and-map-may-no-longer-work (I had to go a bit back in history of that file). So, until Mozilla Rhino/Orchestrator...