Dan Schultzer

Thanks @cunningryan, I've updated the example 😄

Yeah, I think the first option is the best of the bunch. Will have to give it some more thought though as I think there may be a better alternative....

Oh, and just to document this, if form inputs is a good option, then something like this should work: ```elixir defmodule MyApp.Users do @behavior Pow.Ecto.Context alias MyApp.{Accounts, Users.User} @impl true...

> Let me know if you'd like any code based around your first option! Sure, go ahead! I'll just warn you that there may be some pitfalls I haven't thought...

I think I got an alternative that will keep things cleaner since it'll just be added on top of the current setup rather than requiring any changes to the current...

I haven't decided how extensions callback routes should work yet #141, and you can still override the routes by customizing `path_for/5`.

Let me see if next week I can go through this again. Last I worked with it I felt this was too fickle, and not very explicit, so I didn't...

No problem, great to hear that you could fix the issue with the current Pow release! This PR might not be necessary at all.

Sorry for the late reply, I'm swamped with work, recently became a father, and a lot of other life events. Trying to get as much done on Pow as I...

Rephrased, thanks!