Remove Clearance from UsersController. #4201
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
idea behind
Clearance seems not used as originally intended currently. It is based around email/password and provides various helpers. But some of them were already merged into Rails and some of them doesn't work anymore for RubyGems.org since MFA/OTP/WebAuthN... Considering it is sometimes blocking upgrades (thoughtbot/clearance#995) it is IMHO good time to reconsider its usage. At various places it is already overridden and not used.
I do kick-off with off-boarding
Clearance
fromUsersController
. Is is possible to also removeinclude Clearance::Authorization
fromApplicationController
since it is useful only forredirect_back_or
helper which is already present in Rails these days asredirect_back_or_to
. In following PRs I would like to address other controllers and finally theUser
model.