Feature/#310 lastname firstname #72
Merged
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
This includes modifying Person object and behavior of associated Profiles, Accounts, and Users to accomdate seperate Firstname and Lastname fields. The original Name field is retained for migration purposes.
|
All specs passing on local machine |
scherztc
added a commit
that referenced
this pull request
Aug 30, 2015
…tname-firstname Feature/samvera-deprecated#310 lastname firstname
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.
NOTE: This pull request must be merged along with the Shibboleth pull request in the application. The application Gemfile may also need it's Curate gem updated after the merge.
https://scholar-dev.uc.edu is currently running the changes in this branch