ryanwinchester
It’s looking to me like my Oban.Pro.Workflow.add_graft is not adding to context, but in the docs it does
def new_workflow do
Workflow.new()
|> Workflow.put_context(context)
|> Workflow.add_graft(:foo, &graft_foo/1)
|> Workflow.add_cascade(:bar, &bar/1, deps: [:foo])
|> Oban.insert_all()
end
def graft_foo(_) do
Workflow.new()
|> Workflow.add(:foo_id, foo_worker)
|> Workflow.apply_graft()
|> Oban.insert_all()
end
def bar(context) do
%{foo: _} = context
# ...
end
foo will not be in the context…
Where Next?
Trending in Questions
Other Trending Topics
Latest Oban Threads
Latest on Elixir Forum
Sponsor Spotlight
Catch errors, track performance, monitor hosts and more.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 7- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
sorentwo
Confirmed that this is an issue with v1.6.0 (proper). Will have a fix soon for v1.6.1. Thanks for the report, as always
ryanwinchester
With
1.6.1, it’s in the nextadd_cascade, but not in the nextadd_graft. It has reverted back to the original context again.sorentwo
Will you share a minimal example that shows what you’re expecting, so we’re definitely talking about the same code?
ryanwinchester
No, this one was my fault.
I didn’t realize you need to add it to deps for the context to be merged. I only had the step I was waiting on,
e.g. step 3 waits on 2 and step 2 waits on 1.
If I want context from 1 and 2 in step 3, even if I technically only need to wait on 2, I still need to add both as deps to step 3.
ryanwinchester
it appears as though the context is not passing through the grafts in tests though
I’m using the
run_workflow/2function in testssorentwo
None of the context is passing through? Can you share a minimal code example to demonstrate?
Testing with
run_workflow/1is how we’re verifying this functionality, so it’s surprising to hear that it’s working differently for you.ryanwinchester
looks like the same ones missing from earlier
i’m skipping the tests for now. it works as intended manually testing the application
will dig in deeper at another time