Gabe Ruttner

Yes. This is unfortunate. I'm here now.

For registering the step in the workflow are we thinking we'll just add a prop and enforce either run or action? ```ts { run: Function, action: string } ``` for...

Thanks for the ping @mavenraven @semse this change was introduced in https://github.com/hatchet-dev/hatchet-typescript/pull/213 in favor of options, but the change should be backwards compatible with your existing code.

Hi @tolgap thanks for the question. Can you help me understand: > If these Hatchet Tasks have been modified to be provided by a DI container I've stood up the...

I think I actually have a simple pattern here: Modify task to be a factory ```ts import { HatchetClient } from '@hatchet-dev/typescript-sdk'; export type SimpleInput = { Message: string; };...

Yes, you can using the name string -- note you'll obviously need to pass the types into the generic if you want this to be typesafe ```ts const res =...

Hi @AndryHTC have you set `SERVER_AUTH_SET_EMAIL_VERIFIED=true`? https://docs.hatchet.run/self-hosting/configuration-options#authentication-configuration

Thanks for the report @kan2k, fyi deno and windows are not currently in our test matrix but I think should be supported here. I think what we're seeing is not...

hm... i dont think i like this pattern and think what you were going for in the spec makes more sense. can we not expose a register logger or something...

@dresslife-shbh we'd like to improve this one with a fairly large refactor of the filter component to support the growing number of filters and filter conditions. Only issue is we...