Jack Williams

Hi folks! Appreciate the conversation here. It's not a great experience for anyone having to scrape the solution from our docs and, as we've seen, it inevitably goes out of...

As there has been no further feedback since the release (#638) of `@inngest/middleware-sentry` (#598), I'm closing this. Please open another issue referencing that new package for any further requests!

Hi, @riordanpawley! 👋 Thanks for this. We definitely want the types to feel open-ended, hence having our `EventSchemas` class for stacking them and providing them from different sources. We also...

@mattiavitturi Yes! We've discussed this a few times to combat JSON serialization being pretty rubbish; `Date`, as you've found, is usually the first annoyance people run into. [blitz-js/superjson](https://github.com/blitz-js/superjson) would be...

@mattiavitturi Thanks for this thoughtful reply! --- > For our start-up we are using 100% typescript so I can accept to "tie" myself with a transformer. 💯 - This is...

Transferring this to the SDK repo as it'll likely be a change there.

@mcky Transformation is definitely something we'd like to support easily. Typing is the difficulty, for sure. As you can see above, for `superjson` this might be acceptable in the form...

This is great, @maktouch! Thanks for the contribution. In terms of the original issue (#546) and not being able to see which step is causing the problem, would #531 also...

Parallelism in #45 introduces better config for triggers, e.g. ```ts // Any type of function uses the same method. // declare createFunction: (nameOrFunctionOpts, eventNameOrTriggerOpts, fn) => void; inngest.createFunction("...", "demo/event.sent", ()...

Addressed at runtime instead.