Implement similar changes that @cbeer made in https://github.com/sul-… - #2266
Implement similar changes that @cbeer made in https://github.com/sul-…#2266mejackreed wants to merge 1 commit into
Conversation
|
Can you leave a comment, perhaps in source, but at least here, about why When trying to debug engine_cart problems, which I've done my fair share of, I find it enormously helpful to have 'breadcrumbs' left explaining why non-obvious things were done. Even more so when wanting to make changes to the setup, to give you a fighting chance of understanding what you might break by changing something. |
…dlss/sul_styles/pull/35/files to support a default sprockets approach that will still support webpacker
7746814 to
b803bbe
Compare
|
I ran rake locally and all the feature specs failed with: Is |
|
@cdmo 💬
I haven't run it locally w/ this branch, but a hunch: did you regenerate the EngineCart test app after pulling this branch? If so, can you say what Ruby and Rails versions you tested with? (I'm guessing whatever the defaults are when running |
|
Started with a completely fresh clone, checked out this branch, ran EDIT: looks like |
I'll give this a spin today, @cdmo, once I'm done responding to reviews of #2263 Thanks! |
|
@cdmo @mejackreed I was able to pull this branch and see all specs pass. Here's what I did: # start off clean
$ rm -rf .internal_test_app Gemfile.lock
# specify Rails version
$ export RAILS_VERSION=6.0.2.1
# tell EngineCart to skip webpack
$ export ENGINE_CART_RAILS_OPTIONS="--skip-webpack-install"
# install dependencies
$ bundle
# spin up solr in background
$ docker-compose up -d solr
# run default task (build app, run specs)
$ rakeWorked like a charm. Incidentally, these are the same steps I've been using as part of work on docker-compose. See also the new documentation for that: https://github.com/projectblacklight/blacklight/wiki/Testing-and-Developing-Blacklight |
|
@cdmo can you give ☝️ a run-through and confirm it works and is sensible? And then, assuming so, mind re-reviewing? Want to make sure we have 💯 approvals before merging. |
|
@cdmo Amending what I wrote above: these steps worked because the Rails server did not get spun up. Running |
|
Closing this for now. I think we have some other options to resolve Blacklight / Rails 6 / Webpacker |
Now when the test app is generated with Rails 6, the `blacklight:server` actually spins up instead of screaming about webpacker. Related to #2266
Now when the test app is generated with Rails 6, the `blacklight:server` actually spins up instead of screaming about webpacker. Related to #2266
Now when the test app is generated with Rails 6, the `blacklight:server` actually spins up instead of screaming about webpacker. Related to #2266
Now when the test app is generated with Rails 6, the `blacklight:server` actually spins up instead of screaming about webpacker. Related to #2266
Now when the test app is generated with Rails 6 (and Sprockets 4), the `blacklight:server` actually spins up instead of screaming about webpacker. Related to #2266
Now when the test app is generated with Rails 6 (and Sprockets 4), the `blacklight:server` actually spins up instead of screaming about webpacker. Related to #2266
Now when the test app is generated with Rails 6 (and Sprockets 4), the `blacklight:server` actually spins up instead of screaming about webpacker. Related to #2266
…dlss/sul_styles/pull/35/files to support a default sprockets approach that will still support webpacker
This only changes the test app generated.