Mikkel Malmberg

Why are you mentioning me? I have nothing to do with this project?

Nice debugging, thank you! I think we'd need a special page with what used to be in `create.html.erb`, as redirecting to sign in is going to confuse people, I think....

Hi! Thanks! I'm not sure I want built-in devise integration. I'd like to keep the two separate. If we just move to use Devise's `sign_in` method we have to depend...

Hi @grekko! I think the two can co-exist with the _"fix"_ I posted above? Just put Passwordless in front of Devise and let it fall back if necessary. The user...

If you have any specific concerns about mixing the two let me know – I'll see if we can figure something out. But I think going for the simplest possible...

Passwordless doesn't touch ApplicationController unless told to (by using `include Passwordless::ControllerHelpers` in the case of `sign_in`). You could make your own `sign_in` method that takes this into account. I'm very...

Thanks a lot. I suppose we could avoid `isolate_namespace` if we instead prefixed routes with `passwordless_sign_in_path` fx. This would though be trouble if an app has several records that log...

@abevoelker Very ok! Nice work 👏

You're right – no built-in way at the moment. You could override the views to show the sign-in form on the page where users end up on unsuccessful attempts.

This is scheduled for 1.0 (#89) but there's no timeline for when that will be done. The `passwordless_for` method is merely a helper for mounting the engine. See [router_helpers.rb](https://github.com/mikker/passwordless/blob/master/lib/passwordless/router_helpers.rb) to...