Skip to content

Redefine valid_child_concerns #94

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.

Sign up for GitHub

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

Merged
ShanaLMoore merged 1 commit into from
Nov 17, 2025
Merged

Redefine valid_child_concerns #94

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions config/initializers/hyrax.rb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,4 +23,11 @@
# Injected via `rails g hyku_knapsack:work_resource OralHistory --flexible`
config.register_curation_concern :oral_history
end

# Ensure that only the registered concerns can be nested within each other
# Hyrax::NestedWorks loads the valid_child_concerns prior to the above configuration
# This removes Hyku's default work types from the list of valid child concerns
Hyrax.config.curation_concerns.each do |concern|
concern.valid_child_concerns = Hyrax.config.curation_concerns
end
end
Loading