-
Notifications
You must be signed in to change notification settings - Fork 129
Flexible lay ground work #7126
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
base: main
Are you sure you want to change the base?
Flexible lay ground work #7126
Conversation
Test Results 13 files ±0 13 suites ±0 2h 48m 46s ⏱️ + 5m 10s Results for commit e02daec. ± Comparison against base commit b8cdb49. This pull request removes 360 and adds 360 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
This is a good start, and I'm on board with the deprecations. 👍 |
…orm behavior as needed
4c6a3f4
to
035258f
Compare
…/hyrax into flexible-lay_ground_work
@@ -42,7 +42,7 @@ | |||
end | |||
end | |||
|
|||
describe 'create collection type' do | |||
describe 'create collection type', :clean_repo do |
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.
fixed a flapping spec that was making me crazy ;-)
Summary
Lays the groundwork for Flexible metadata by making including core and basic metadata by default completely optional and toggled by config variables. This version allows configuring the Collection, AdministrativeSet, FileSet and each individual work type independently.
It depreciates two existing functions in a way that if you are using them you won't have to make changes right away.
The first is that Hyrax includes core_metadata in all work types. This can still be done in the future but should be explicit in each work types class and the generators have been updated to support that.
The second is the removal of the auto inclusion of
"#{SchemaName}FormFieldsBehavior"
when addingschema_name
schemas to the form objects. This is difficult to trace as there is no explicit in include so its hard to know where this code comes from when one is debugging. It also doesn't save much in terms of LOC to have it explicit. In current Hyrax this is only used by based near. based_near form attributes have been moved to be generally included but to noop if the object doesn't have a based near field instead.This is step 1 or arguably step 0 of the flexible metadata work. My plan is to chain additional PRs off this one so that they can be reviewed and merged in order only.
@samvera/hyrax-code-reviewers