-
Notifications
You must be signed in to change notification settings - Fork 76
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
Refactor legacy User
model
#1802
Merged
josephsnyder
merged 13 commits into
Kitware:master
from
williamjallen:legacy-user-model-refactor
Nov 17, 2023
Merged
Refactor legacy User
model
#1802
josephsnyder
merged 13 commits into
Kitware:master
from
williamjallen:legacy-user-model-refactor
Nov 17, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
As of PHP 8, password_hash() only ever returns a string. No need to have a wrapper function checking for a return value of false.
josephsnyder
approved these changes
Nov 17, 2023
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.
All the user interactions I can test manually look unchanged from a user's POV. I think this is a great change.
sbelsk
pushed a commit
to sbelsk/CDash
that referenced
this pull request
Nov 20, 2023
We currently have two user models: a legacy model, and an Eloquent model. The reflection approach used to access legacy model members through the Eloquent model is not conducive to static analysis, and is a pain to work with. This PR moves a significant portion of the legacy model logic to the Eloquent model. Additionally, I have improved the User<->Password model relationship.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We currently have two user models: a legacy model, and an Eloquent model. The reflection approach used to access legacy model members through the Eloquent model is not conducive to static analysis, and is a pain to work with. This PR moves a significant portion of the legacy model logic to the Eloquent model. Additionally, I have improved the User<->Password model relationship.