-
Notifications
You must be signed in to change notification settings - Fork 109
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
[don't merge] Refactor CSS assets to use Sprockets instead of Webpack #1864
Conversation
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.
Changes look ok. Its really hard to tell though if there are any visual issues with the CSS reorg without running and visually inspecting the site.
Why move back over to Sprockets (aside from being more Rails-ish)? What advantage are we gaining? We would still need to support Webpack to handle our ES6 JS.
If I remember well, we decided to move towards npm to handle front-end related issues since they are more actively maintained than front-end assets handled through ruby gems. Although these changes certainly keep the codebase more Rails focused, I got my doubts whether or not it is an appropriate move knowing that Rails 5 introduced Webpack on their assets pipeline... |
3793647
to
ea456fc
Compare
f282876
to
2e2743f
Compare
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.
Really like the refactoring out of variables and hierarchical layout.
I'll need to have a look through all the customization we're using and make sure everything we're changing is captured in the variables.
There was a bug that caused the error message to popup when all of the sections within a phase were modifiable.
2e2743f
to
36ba718
Compare
dc07157
to
27561a5
Compare
Readme should be updated to include: Assets ManagementJavascriptsJavascript are written using ES6 and can be found in You don't have to run a separate process for Webpack for JS to be compiled. This is compiled automatically on each request (in development). Be sure to check the Rails log if you are seeing unexpected Javascript behaviour. There's an ESLint check run each time the assets are compiled, and errors are reported in the Rails log. Stylesheets, images and other assetsStylesheets are written using Sassy CSS (via lib-c SASS) Stylesheets use Rails' asset pipeline for compilation. For more information on how that is configured, please read this guide: https://guides.rubyonrails.org/asset_pipeline.html CompilingTo compile assets for development, please use the rake task |
👍 The changes look fine to me. I will need to do some updating of the customized CSS for the DMPTool once this is in place. It would be good to write up some recommendations/suggestions for how to go about customizing the CSS for local installations. Feel free to merge into dev while I'm away |
This reverts commit fb3edd3953ffc019ffdc21a366c734c43ca44271.
114bb38
to
d51fd87
Compare
fc9eefc
to
c102270
Compare
c102270
to
c86beab
Compare
@Bodacious as this is pointed at the next-sprint branch, is there still reason not to merge it into that branch? |
@xsrust Let me have another look at it and make sure it's ready. |
Please ignore this. Prefer #1962 |
would suggest just closing this PR in favor of #1962 |
Fixes #1862, #1762
Changes proposed in this PR:
app/assets
rake assets:precompile
to support JS and CSS