Keep in mind that Ecto changesets do not need to be tied to a database at all. All of our live view forms ultimately make GraphQL API calls, but we still use changesets for the convenience of providing “client side” validation. Then we just Ecto.Changeset.apply_changes on a valid changeset, and take the resulting map and send it over the network to the API.
Thanks for the help! I upgraded and cleaned everything. But It turned out that that error was from pushing it against a different property in the assigns map.
Progress: I can now submit all my values using that setup!
But they don’t display on mount or after assigning them from the phx_submit event.
I can display other liveview values though by using that event to apply things in the leex like <%= @some_value %>.
Hey Ben, I was wondering, do you have an example repo as to how one would integrate Phoenix LiveView and Absinthe GraphQL? Thanks in advance for any additional information that you can provide regarding this topic.