AshOban trigger `read_metadata` passed to action as argument?
Hello!
In the AshOban code, there is this documentation statement: https://github.com/ash-project/ash_oban/blob/main/lib/ash_oban.ex#L129
I can't see where metadata is passed to the update action. I presume it would be somewhere here: https://github.com/ash-project/ash_oban/blob/main/lib/transformers/define_schedulers.ex#L477-L492
What am I missing? Has this part of the feature been missed, or was it never the intention to grab the metadata back out of the Oban job table into Ash land again?
GitHub
ash_oban/lib/ash_oban.ex at main · ash-project/ash_oban
An Ash extension for interacting with Oban. Contribute to ash-project/ash_oban development by creating an account on GitHub.
GitHub
ash_oban/lib/transformers/define_schedulers.ex at main · ash-projec...
An Ash extension for interacting with Oban. Contribute to ash-project/ash_oban development by creating an account on GitHub.
2 Replies
Hm…this looks like maybe a commit didn’t make it in or something.
When I originally made the feature I ended up not needing it, and we can’t run tests in the repo because we’re missing an oban license
ah right
if you happen to have the commit lying around and can incorporate it, I am happy to test it in the app I'm working on
being able to send an argument to the action a trigger runs will be very helpful in parameterisation