Resource Key in Form Setup for Nested Union Forms

If it would be fixed it would be fixed by cast_tag?: false not true. If that doesn’t help we may need to get a reproduction project going so I can debug properly

Typo. I meant (and did) false

Can I see the resource represented by OneOfTheUnionTypes?

Here’s what it looks like:

defmodule AshUnionIssueWeb.Resources.OneOfTheUnionTypes do
  use Ash.Resource, data_layer: :embedded

  attributes do
    uuid_primary_key :id
    attribute :prompt, :string, allow_nil?: false, public?: true
    attribute :response, :string, public?: true
  end

  actions do
    default_accept [:prompt, :response]
    defaults [:create, :read, :update]
  end
end

But I did one even better - I reproduced the issue in this repo. You can check it out.

Thank you for the reproduction Please try out main of ash. It will likely be a few days before a proper release can be cut, sorry about that

Thanks for all your help, Zach

Once I’m able to clone ash, I’ll test it. It seems to be broken right now:

error: invalid path 'documentation/dsls/DSL:-Ash.DataLayer.Ets.md'
error: invalid path 'documentation/dsls/DSL:-Ash.DataLayer.Mnesia.md'
error: invalid path 'documentation/dsls/DSL:-Ash.Domain.md'
error: invalid path 'documentation/dsls/DSL:-Ash.Notifier.PubSub.md'
error: invalid path 'documentation/dsls/DSL:-Ash.Policy.Authorizer.md'
error: invalid path 'documentation/dsls/DSL:-Ash.Reactor.md'
error: invalid path 'documentation/dsls/DSL:-Ash.Resource.md'

wait you’re also having this problem? That is very strange are you using windows? I don’t see how this is something I could fix in Ash. Does windows have a problem with certain characters in file names or something?

Yeah, I ran that from a windows

I was going to check on a Mac yesterday but I got sidetracked.

I might not be able to get to it today either but once I do, I’ll let you know.

Hi, Zach. Apologies for the lag. Work on this had to pause for a bit.

Sadly, even on main of ash, the NoSuchInput error persists in the repo

Not sure how to proceed

Thanks for the heads up. I will look into this tomorrow.