Zach Daniel
Zach Daniel
Hmm...yes. It could be supported in filters exposed over GraphQL for example without being exposed as a field.
I'd like to leave this open for a while to hear other perspectives. My current line of thing is that having `allow_nil?: false` would have been a better choice originally,...
That is true. It's a fair point and does sway me a bit. For end users we can relatively easily write an igniter script that does the upgrade. So we...
Feel free to promote this a bit in the discord or on ElixirForum to see what people think.
I agree. Ultimately though I just can't imagine this being worth it to change 😓. Maybe in Ash 5 😆
It's just *so much work*. Every extension that adds an attribute expecting it to be `allow_nil?: true` by default has to be updated. If I could go back in time...
I guess I just couldn't imagine myself making this change anytime soon. If you or someone else wants to visit all of our core supported extensions and add `allow_nil?: true`...
You have to first `require Ash.Sort`
Yeah, that would make sense to me 😄
Oh, I would not try to an analyze the expression yourself. just make sure that the error from `hydrate_refs` gets returned instead of a pattern match error.