confirm_success_url shouldn't be a required param

[aesnyder]

I'm probably missing the point but...

It seems odd that devise_token_auth requires me to pass a confirm_success_url with the creation of the user.

While it is nice to be able to control this at the request level, I would think that it's default behavior should be to use a default confirm_success_url defined somewhere in the rails layer.

I'm happy to open a pr, but wanted to get some weigh-in on where this makes the most sense to be defined?

[nicolas-besnard]

I don't understand why this is set on the front side. I think the best solution should be to determine the URL on the configuration file of this gem.

[aesnyder]

I agree I plan to add a commit to have a default confirm success url in the
rails config.

I can add.

On Tuesday, March 10, 2015, Nicolas Besnard [email protected]
wrote:

I don't understand why this is set on the front side. I think the best
solution should be to determine the URL on the configuration file of this
gem.

—
Reply to this email directly or view it on GitHub
#176 (comment)
.

[lynndylanhurley]

The confirm_success_url param is used to support multiple client applications. If the param isn't required, then the API has no way of knowing where to redirect after email confirmation.

I'm open to allowing an optional default confirm_success_url to be set on the API. Feel free to send a PR if you have time.

[lynndylanhurley]

I just pushed a fix for this in version 0.1.32.beta8. You can now set defaults for the email confirmation and password reset redirects. See the config section of the readme for more info.