dblack Posts - Answer Overflow

dblack

•Created by dblack on 4/10/2023 in #showcase

One-to-many Form Example

I've put together a little example of using AshPhoenix.Form to build an interactive one-to-many form: https://github.com/totaltrash/form_example I picked up Ash around the same time I got into Elixir (both Ash and Surface blew my mind at the time, so much declarative goodness). As I've never really worked with Ecto directly, I absolutely loved this post (https://kobrakai.de/kolumne/one-to-many-liveview-form) on building a one-to-many form using Ecto changesets - I began to understand how Ecto was never built with this interactive use case in mind, and the complexities involved of rolling your own solution. AshPhoenix.Form just handles this stuff out of the box, so I had to model something similar using Ash and AshPhoenix.

4 replies

AEAsh Elixir

•Created by dblack on 3/29/2023 in #showcase

Filter Form Example

I was doing a bit of a proof of concept with AshPhoenix.FilterForm, so I thought I'd roll up a little example application: https://github.com/totaltrash/filter_form_example Hopefully it might be useful to anyone who wants to try out complex nested filter forms.

5 replies

AEAsh Elixir

•Created by dblack on 3/28/2023 in #support

`form_for` deprecation warning when using FilterForm

I'm getting a deprecation warning filling up the terminal (I'll blame that for the earlier inspect non-issue!):

warning: form_for/3 without an anonymous function is deprecated. If you are using Phoenix.LiveView, use the new Phoenix.Component.form/1 component
  (phoenix_html 3.3.1) lib/phoenix_html/form.ex:341: Phoenix.HTML.Form.form_for/3
  (elixir 1.14.3) lib/enum.ex:1658: Enum."-map/2-lists^map/1-0-"/2
  (phoenix_live_view 0.18.18) lib/phoenix_component.ex:2266: Phoenix.Component."inputs_for (overridable 1)"/1
  (phoenix_live_view 0.18.18) lib/phoenix_live_view/tag_engine.ex:68: Phoenix.LiveView.TagEngine.component/3
  (my_app 0.1.0) lib/my_app_web/live/filter_form_live.ex:65: anonymous fn/2 in MyAppWeb.FilterFormLive.filter_form_component/1
  (phoenix_live_view 0.18.18) lib/phoenix_live_view/diff.ex:517: Phoenix.LiveView.Diff.invoke_dynamic/2
  (phoenix_live_view 0.18.18) lib/phoenix_live_view/diff.ex:398: Phoenix.LiveView.Diff.traverse/7
  (phoenix_live_view 0.18.18) lib/phoenix_live_view/diff.ex:544: anonymous fn/4 in Phoenix.LiveView.Diff.traverse_dynamic/7
  ...

warning: form_for/3 without an anonymous function is deprecated. If you are using Phoenix.LiveView, use the new Phoenix.Component.form/1 component
  (phoenix_html 3.3.1) lib/phoenix_html/form.ex:341: Phoenix.HTML.Form.form_for/3
  (elixir 1.14.3) lib/enum.ex:1658: Enum."-map/2-lists^map/1-0-"/2
  (phoenix_live_view 0.18.18) lib/phoenix_component.ex:2266: Phoenix.Component."inputs_for (overridable 1)"/1
  (phoenix_live_view 0.18.18) lib/phoenix_live_view/tag_engine.ex:68: Phoenix.LiveView.TagEngine.component/3
  (my_app 0.1.0) lib/my_app_web/live/filter_form_live.ex:65: anonymous fn/2 in MyAppWeb.FilterFormLive.filter_form_component/1
  (phoenix_live_view 0.18.18) lib/phoenix_live_view/diff.ex:517: Phoenix.LiveView.Diff.invoke_dynamic/2
  (phoenix_live_view 0.18.18) lib/phoenix_live_view/diff.ex:398: Phoenix.LiveView.Diff.traverse/7
  (phoenix_live_view 0.18.18) lib/phoenix_live_view/diff.ex:544: anonymous fn/4 in Phoenix.LiveView.Diff.traverse_dynamic/7
  ...

Line 65 of my component is the call to <.inputs_for :let={components} field={@component[:components]}>... I think the warning is referring to the call to form_for at https://github.com/ash-project/ash_phoenix/blob/main/lib/ash_phoenix/filter_form/filter_form.ex#L948 but not totally sure

11 replies

AEAsh Elixir

•Created by dblack on 3/28/2023 in #support

FilterForm inspect strange behavior

I'm just playing around with FilterForm and I'm seeing some weird inspect behavior, which is not making it easy to reason with what's going on. For instance:

filter_form = FilterForm.new(Property)
{filter_form, group_id} = FilterForm.add_group(filter_form, operator: :or, return_id?: true)
filter_form = FilterForm.add_predicate(filter_form, :id, :eq, nil, to: group_id)

IO.inspect(filter_form)

filter_form = FilterForm.new(Property)
{filter_form, group_id} = FilterForm.add_group(filter_form, operator: :or, return_id?: true)
filter_form = FilterForm.add_predicate(filter_form, :id, :eq, nil, to: group_id)

IO.inspect(filter_form)

Gives me:

%AshPhoenix.FilterForm.Predicate{
  id: "0b9cab33-2194-475e-a010-407d5964a8ec",
  field: :id,
  value: nil,
  transform_errors: nil,
  operator: :eq,
  params: %{
    "field" => :id,
    "id" => "0b9cab33-2194-475e-a010-407d5964a8ec",
    "operator" => :eq,
    "value" => nil
  },
  arguments: %AshPhoenix.FilterForm.Arguments{
    input: %{},
    params: %{},
    arguments: [],
    errors: []
  },
  negated?: false,
  path: [],
  errors: [],
  valid?: true
}

%AshPhoenix.FilterForm.Predicate{
  id: "0b9cab33-2194-475e-a010-407d5964a8ec",
  field: :id,
  value: nil,
  transform_errors: nil,
  operator: :eq,
  params: %{
    "field" => :id,
    "id" => "0b9cab33-2194-475e-a010-407d5964a8ec",
    "operator" => :eq,
    "value" => nil
  },
  arguments: %AshPhoenix.FilterForm.Arguments{
    input: %{},
    params: %{},
    arguments: [],
    errors: []
  },
  negated?: false,
  path: [],
  errors: [],
  valid?: true
}

I would have expected a FilterForm struct. I've validated that filter_form is actually a FilterForm and not a FilterForm.Predicate? Is this a bug with the inspect protocol for FilterForm's or am I totally misunderstanding something (likely)!

15 replies

AEAsh Elixir

•Created by dblack on 3/1/2023 in #support

Error with composite `{:array, :atom}` field

I've started to get the following error for no apparent reason - the app was working fine, I've just updated deps and this happens inconsistently (sometime the app works fine, then I'll restart the dev server and it will be broken):

cannot load ``["admin"]`` as type {:array, {:parameterized, Ash.Type.Atom.EctoType, []}} for field :roles in #Crm.Accounts.User

The attribute looks like:

attribute :roles, {:array, :atom} do
  allow_nil? false
  default []
  constraints nil_items?: false
end

attribute :roles, {:array, :atom} do
  allow_nil? false
  default []
  constraints nil_items?: false
end

2 replies

AEAsh Elixir

•Created by dblack on 2/19/2023 in #support

Concat with nil values

The built in concat calculation returns nil when any of the values it is concating is nil. I need a nil friendly concat and I could use something like this (which only works on the data layer and is postgres specific):

  calculate :full_name,
            :string,
            expr(fragment("concat_ws(?, ?, ?)", ", ", first_name, last_name))

  calculate :full_name,
            :string,
            expr(fragment("concat_ws(?, ?, ?)", ", ", first_name, last_name))

I'd prefer to write a custom calculation that I can reuse (so the calculation can be run in Ash land after the record is retrieved from the db), but if I create a custom calculation (to use concat_ws) it is still only going to be suitable only for postgres datalayer. Is there a way that ash_postgres could use concat instead of || as an option? I'm probably overthinking it and should just use the above calc and move on!

55 replies

Gaming

Programming