Docs: Proposal: Add guidelines how to handle workflow/activity dependencies for the Go SDK about documentation HOT 4 CLOSED

thanks for the note Sebastian!

guidelines how to handle dependencies (like services, database access layers, etc.) in Go based workflows/activities.

1. i'm not sure i understand why you want Temporal to give you guidance on these things. The point of having idiomatic language SDKs is that it'd plug right in to your normal development workflow?

I struggled with getting the correct workflow name in workflow instances

2. i'm interested in hearing more as that is something we can probably help with. An example would be nice!

3 ideas for how to do this:

• book a call with me: https://savvycal.com/swyx/quick
• record async video describing your situation (Loom helps) and email it to us [email protected]
• write a minimal example repro to demonstrate the problem and ask how we'd solve it?

from documentation.

hey Sebastian gonna close this for now, please feel free to reopen if you'd like to follow up on this!

from documentation.

Hey swyx,

didn't expect to see you here as I know you from the React/Svelte community :D

Let's take the ecommerce example to make it more clear: https://docs.temporal.io/blog/build-an-ecommerce-app-with-temporal-part-2-reminder-emails#sending-emails-from-an-activity

In this activity, the dependencies (like the mailing service) are tightened to the activity function. But I would like to pass the depedencies via the function params to be able to write good tests for it. From my understanding, these params must be serializable and always flow through the workspace code.

Can you show me how it's supposed to work in this situations? I have the same question for workspaces (which could also have deps that arent serializable).

from documentation.

@SebastianM
You can pass these types of dependencies to your activities when you register them with the worker, don't have to hard-code them in your activities as done in that example.
Another thing the Temporal testing framework provides is mocking of activities, which would allow you not to use the "real/prod" services that your activities may interact with, during unit/integration testing.

Feel free to ask any questions you might have on our community forum - https://community.temporal.io :)

from documentation.