Some routes changes about phoenix_token_auth HOT 8 CLOSED

@manukall :)

from phoenix_token_auth.

hey @OpakAlex
i don't see the reason to change it. what's the use case or problem you're running into?

from phoenix_token_auth.

I may add that i dont like very much that there are

      post  "users",                 PhoenixTokenAuth.Controllers.Users, :create
      post  "users/:id/confirm",     PhoenixTokenAuth.Controllers.Users, :confirm

This takes for granted that the "user" model is called users.

I successfully managed to make it use the "Account" model ( taken idea from your use of account model )

from phoenix_token_auth.

@alexjp Account model it's not user. In real projects you have User and Account. I think we need do get request to users, not to accounts.

from phoenix_token_auth.

it's pretty easy to just define your own routes. just instead of putting PhoenixTokenAuth.mount into your router define them manually as that macro would.

from phoenix_token_auth.

@manukall definitly.
Later at night, can i do a pull request to the documentation ? "Customizing routes?"

from phoenix_token_auth.

@alexjp that would be extremely great 😃

from phoenix_token_auth.

+1

from phoenix_token_auth.