Ali Cherry

Hello, Is it possible to move the functionality of determining the target method from AbstractRestfulController's onDispatch to somewhere prior dispatch? I've provided a fix for this, specific for my purpose,...

Hi @AlexZ-343, I'm facing this issue as well. There's a fix by the node team in https://github.com/nodejs/node/pull/44109. I am going to test it using node [v19.0.0-nightly20220806760ecc9c75/](https://nodejs.org/download/nightly/v19.0.0-nightly20220806760ecc9c75/) that includes it. if...

I've created a playground here: [testdouble-ts-node-esm-playground](https://github.com/alichry/testdouble-ts-node-esm-playground). Mocking `fs` succeeded, however, mocking internal modules written in typescript did not. The outcome is identical when using node `v18.7.0` or node `v19.0.0-nightly20220806760ecc9c75`

> Could you clarify what you mean by this statement? Hi @AlexZ-343 👋, whoops, sorry about that. `internal` is a bit ambiguous since internal modules often refer to internal nodejs...

Hey @searls, thank you for the release! I've set it to 0.6.14 instead of the fix's commit hash. I've noticed no changes whatsoever; what am I missing?

See https://docs.spaceuptech.com/microservices/deployments/deploy-custom-code/ > Before we can deploy our service, we need to make sure that you have configured your Space Cloud project for which container registry to publish the docker...

I'll add a PR to specify this limitation in the docs.

It might be desirable to refactor and introduce `isPipelineResolverProps` instead of relying on `isDataSourceResolverProps` ⬇️ ```ts private isDataSourceResolverProps(object: AppSyncApiResolverProps): boolean { return object.dataSource !== undefined; } + private isPipelineResolverProps(object: AppSyncApiResolverProps):...

While the exception is caught and printed, this is output SVG:  After applying the below patch to `parser.js`→`getClassOrInterfaceName`, ```diff ... if (classOrIf instanceof SimpleAST.Type) { - name = classOrIf.getSymbol().getName();...

Thank you for your response @demike. I have submitted a PR to fix the first issue. I have this snippet in my workshop: ```ts // parser.ts /* introduce new function...