Zach Daniel
Zach Daniel
This makes perfect sense to me, and seems like it is only a benefit w/ no downside. PR welcome!
In this case it would make sense to DRY it up yeah 😄
I think the trick will be to add some kind of "handler" that can return `:snooze`/`:cancel` statuses. For instance we have an `on_error` action that can currently handle errors, so...
Yeah, so in the long run we need to create something like this: ```elixir defmodule MyApp.AdminUI do use AshAdmin.UI ... end ``` Which we could put custom links in at...
That sounds great! I put it on the roadmap for "someday", but would be very happy to see it done much earlier
PR welcome!
Great idea :)
Yep! You could take a look at how the task is implemented in AshAuthentication as well. That should be a basis for this :)
We could then add an alias for `mix phx.routes` that calls this task after calling phx.routes 🎉
We should probably validate inputs first? Or require that inputs is a map? That second one would be a breaking change. Anyway, definitely confusing.