-
Notifications
You must be signed in to change notification settings - Fork 0
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
Potential Issues Around Knapsack and Rails.root #1
Comments
14 tasks
jeremyf
added a commit
to scientist-softserv/adventist_knapsack
that referenced
this issue
Oct 9, 2023
This is now obviated by upstream Hyku. Prior to this commit, we were looking in `Rails.root` but we needed to first interogate the Knapsack and then Rails.root. Related to: - samvera/hyku#2010 - samvera/hyku#2012 - #60 - samvera-labs/hyku_knapsack#1
jeremyf
added a commit
to scientist-softserv/adventist_knapsack
that referenced
this issue
Oct 10, 2023
This is now obviated by upstream Hyku. Prior to this commit, we were looking in `Rails.root` but we needed to first interogate the Knapsack and then Rails.root. Related to: - samvera/hyku#2010 - samvera/hyku#2012 - #60 - samvera-labs/hyku_knapsack#1
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In Hyku and Hyrax there are long-standing references to
Rails.root
. This works when Hyku is the base application. However, with Knapsack, we need to consider an alternate approach toRails.root
.The issue is as follows:
Rails.root
resolves to the root of the Hyku applicationA proposed solution for Hyku is available here:
We'll also want to add a rubocop to indicate the
Rails.root
is an anti-pattern.However, Hyrax also uses
Rails.root
to reference static files. I usedrg Rails.root app lib --files-with-matches | awk '{ print "- [ ] " $1 }
to generate the list of files that need reviewing:This is repeated in:
The text was updated successfully, but these errors were encountered: