Repository navigation
Removes creator from admin set form - #7370
Merged
Merged
Conversation
Creators on admin sets are set in a transaction step, and anything used in the form is overridden by the transaction step. This change removes the creator requirement from the form, and returns to previous behavior of allowing the creator to be set in the transaction step.
Test Results 13 files ±0 13 suites ±0 2h 59m 56s ⏱️ + 2m 44s Results for commit 4968cc1. ± Comparison against base commit 8f7f0b5. This pull request removes 366 and adds 369 tests. Note that renamed tests count towards both.♻️ This comment has been updated with latest results. |
orangewolf
previously approved these changes
Mar 3, 2026
The spec was not taking renamed properties into account. Now that the validator handles renamed properties, the spec should as well.
ShanaLMoore
approved these changes
Mar 3, 2026
This file contains hidden or 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
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.
Creators on admin sets are set in a transaction step, and anything used in the form is overridden
by the transaction step. This change removes the creator requirement from the form, and returns
to previous behavior of allowing the creator to be set in the transaction step.
Fixes
Ref samvera/hyku#2931
Summary
In the past, creator was hidden and just assigned as the user key (email) through the code, but it has to be defined on the object, so it was added into the m3 profile. This requirement caused it to be shown on the form but not actually used because it was being loaded as it always has been.
By updating the m3 profile, it can be renamed on the profile via the
name:key (I am usingcreator_hiddenas the renamed term) and then it can be hidden from the form and behave as it did in prior versions.Additionally, required terms added to the m3 profile via the
name:key on the property were not recognized as present in the validator. This issue is addressed as well.