You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
supply resources (DB, verb clients) to verbs explicitly— replacing ftl.Call(...), db.Exec(...) etc. (inspired by the pattern of injecting resources @stuartwdouglas implemented for the JVM)
need a way of knowing deterministically which resources a given verb uses. investigate/propose ways to accomplish this
The text was updated successfully, but these errors were encountered:
https://hackmd.io/OULeRFQQQvaMURysN27eEw
only the TestLifecycle integration test is updated with the new approach
in this PR, to demonstrate that both old and new verb call strategies
are still functional. will remove other usages of `ftl.Call(...)` to
follow
- generates `<Verb>Client` signatures in external stubs and (local)
signatures in `types.ftl.go`
- generates resource registrations in `main.go` and `types.ftl.go`, e.g.
"providers" for verb clients
-`go-runtime/build.go` changes accompanying the above^ bunch of stuff to
get imports working now that we're generating full verb request/response
types rather than just function references
- updates `go-runtime/server.go` to inject the registered providers when
processing an inbound call
#2641
---------
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
supply resources (DB, verb clients) to verbs explicitly— replacing ftl.Call(...), db.Exec(...) etc. (inspired by the pattern of injecting resources @stuartwdouglas implemented for the JVM)
need a way of knowing deterministically which resources a given verb uses. investigate/propose ways to accomplish this
The text was updated successfully, but these errors were encountered: