Gabriel Cangussu

I was able to implement a working version of this tool, but I couldn't do it without adding more arguments to the `pluck` call signature: ```typescript import { buildInfo }...

To solve this repetitive pattern ```javascript const rootField = 'myRootField'; const operation = 'myOperation'; const newInfo = pluck(rootField, operation, ctx.db.schema, 'myFieldName', info); const field = await ctx.db[operation][rootField]({...}, newInfo); ``` We...

@ry5n I've ran into the same problem, the solution was to mark the entry as deleted and adjust our models to ignore entries marked as deleted. We use a timestamp...

> @manast If there was a way to specify how the process is spawned (command arguments?) then this problem would be easier to solve, at least with tsconfig-paths. We could...

Here is a custom resolver that solved problems to us: https://gist.github.com/gcangussu/af52da296aef829eba15ea626453f031 We are using Bazel.

@ACollectionOfAtoms I'm not sure if Jest will use the custom resolver to resolve the test suite file. I think it only uses it to resolve the modules you `require()`. Maybe...

This affect us as well, the warning show up every time we install/change dependencies. I can report that we've been using this package with [email protected] without any issues for the...