Ecto.Schema vs a behavior or protocol

[cckkaallee]

Hi,

I'm interested in using inertia with ash framework. Found this thread here: https://elixirforum.com/t/has-anybody-tried-to-use-ash-inertia-js-together/68348/4

Wanted to ask what your thoughts are on using a protocol or behavior that then uses Ecto.Schema to easier allow more alternative integrations?

[derrickreimer]

I'm not very familiar with Ash Framework, but it seems like the core request here is to structure Inertia.Errors as a protocol, so that you can do something like this?

defimpl Inertia.Errors, for: Ash.Changeset do
  def compile_errors!(changeset) do
    # ...
  end
end

This would definitely be an improvement over the existing structure, which requires you to pass either custom map or Ecto.Changeset to assign_errors.

Regarding the broader claim of reliance on Ecto.Schema, I'm not totally sure what the ideal solution looks like. All this library does at the moment is takes whatever you pass it (e.g. via assign_prop) and casts it to JSON when serializing it. You can freely pass pre-serialized maps (instead of structs) to assign_prop if you don't want to rely on auto-JSON encoding. Is the desire here to have a separate protocol for serializing prop values, like defprotocol Inertia.Prop ...?

[zachdaniel]

Makes sense to me! If this project gets an igniter installer then I'd definitely put that up in our installer :D

[andresgutgon]

I have inertia running with a custom Esbuild and pnpm. But I was wondering if someone was considering Vite instead. This is great news for me 🎉

[andresgutgon]

For me the drawback of using ESBuild for JS code is that is doesn't have HMR. Maybe I'm mistaken. If this were this way I think is a big reason to move to Vite

[derrickreimer]

Certainly nothing stopping folks from using other build systems! My plan for the moment is to keep inertia-phoenix as close to the default Phoenix stack as possible by default. I don't believe esbuild has HMR, but I have found the Phoenix auto-reload behavior when the JS build updates to be pretty effective for development flow.

[andresgutgon]

You have infinitely more experience than me with this stack : )
I'm coming from React stacks and I'm used to the hmr experience. It's awesome everything is possible. Thanks!