I am trying to create a code interface that is powered by a query that will grow and evolve over time. To just play around with Ash queries I tried to start easy and return all the resources where the attribute word is "red". This code works: require Ash.Query Red.Practice.Card |> Ash.Query.filt…

[image] zachdaniel: filter expr(retry_at < now() and user_id == ^actor(:id)) By Golly it works :tada::partying_face::bottle_with_popping_cork: If anyone else is still following along and wants a complete example, here is the now-beautiful interface that can be used elsewhere in the applicati…

There are a couple elements that you’re going to need for this. Expressions — ash v3.29.3 The expressions guide shows examples of the kinds of things you can do with expr. In your case what you’re looking for is filer expr(is_nil(retry_at)) What you might en…

Thanks, Zac :tada:. This works to return all the instances of the resource where the attribute is nil: read :next do filter(expr(is_nil(retry_at))) end I’ll report back when I find time to try the rest.

I was able to make the after_action work. Here are my code_interface and action blocks: code_interface do define_for Red.Practice define :create, action: :create define :next, action: :next, args: [:user_id] define :oldest_untried_card, action: :oldest_untried_card, args: [:user…

And then it will be in context.actor (context is the second argument to the prepare function)

I tried this. I went down this path for a while for the purposes of learning, but this code lives outside of the resource and I would want the code interface to expose a single function to anything outside of the resource. # outside of the resource Red.Practice.Card |> Ash.Query.for_read(:next, %{}…

Referencing the actor from a template looks like this: filter expr(retry_at < now() and user_id == ^actor(:id)) Your before action hook never ran because you didn’t return the new query containing the before_action hook. It would look something like this: # inside the action prepare fn query, con…

How to filter using a code interface

Questions & Help Questions

zachdaniel October 19, 2023, 2:27pm 5

The actor should be available as an option to Ash.Query.for_read, does that not work?