-
Notifications
You must be signed in to change notification settings - Fork 229
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make the remember_me_token
cookie name configurable
#179
base: master
Are you sure you want to change the base?
Conversation
|
||
expect(User).to receive(:authenticate).with('[email protected]', 'secret', '1') { |&block| block.call(user, nil) } | ||
expect(user).to receive(:remember_me!) | ||
expect(user).to receive(:remember_me_token).and_return('abracadabra').twice |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why does this receive the token twice? I'm not very familiar with the callback system, but this looks like it might be a side-effect of the double callback bug in 0.13.0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@athix to be honest, I copied it over from the testcase above this one. So it could be part of the double callback bug. When I remove the twice
method though, it gives an error. Could it be that the double callback bug is still relevant?
9d830ec
to
ab9a403
Compare
@athix I've implemented your remarks. Could you take a look again? |
ab9a403
to
03e4973
Compare
@robinvdvleuten It seems that CI failed. |
This PR makes the default
remember_me_token
cookie name configurable to whatever seems to fit for the application.