-
Notifications
You must be signed in to change notification settings - Fork 21.4k
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
Eliminate overlapping app/assets
load path
#21794
Eliminate overlapping app/assets
load path
#21794
Conversation
`app/assets` was added to give `manifest.js` a place to live, but it suggests that `require 'stylesheets/foo.css'` might be the right way to refer to `require 'foo.css'`. We resolve the overlap and clarify that `manifest.js` is config by moving it from `app/assets/` to `app/assets/config/`. Put it up on a pedestal: rails/rails#21794 This reverts rails#232 and commit 39ecb27, reversing changes made to 3a44d47.
@@ -1,4 +1,6 @@ | |||
require 'concurrent' | |||
# FIXME: clean up warning spam from concurrent lib |
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.
I think they are already fixed. Can we just point to master branch of it just to avoid having patches on Rails?
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.
Sure can.
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.
The warnings are fixed, except for ruby-concurrency/concurrent-ruby#419
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.
I plan to publish a new build of concurrent-ruby today. That should fix the warnings. I'll create a Rails PR pointing to the new version as soon as I do.
5fd64f8
to
10b43a2
Compare
@@ -154,6 +154,11 @@ PATH | |||
rake (>= 0.8.7) | |||
thor (>= 0.18.1, < 2.0) | |||
|
|||
PATH | |||
remote: ~/source/concurrent-ruby |
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.
That doesn't sound quite right
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.
😁
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.
🚢
10b43a2
to
8736357
Compare
Bump version to 3.0.0.beta3 `app/assets` was added to give `manifest.js` a place to live, but it suggests that `require 'stylesheets/foo.css'` might be the right way to refer to `require 'foo.css'`. We resolve the overlap and clarify that `manifest.js` is config by moving it from `app/assets/` to `app/assets/config/`. Put it up on a pedestal: rails/rails#21794 This reverts rails#232 and commit 39ecb27, reversing changes made to 3a44d47.
* Move `app/assets/manifest.js` to `app/assets/config/manifest.js`. Avoid the suggestion that you can/should deep-link `stylesheets/foo`. * Pull in all toplevel stylesheets and JavaScripts, not just `application.js` and `.css`. Demonstrate how to use `link_directory` with a specified `.js`/`.css` type. * Fix RAILS_ENV handling in assets tests. * Shush warnings spam from third-party libs that distract from tests.
8736357
to
20ec1e9
Compare
…rom-toplevel-to-config-subdir Eliminate overlapping `app/assets` load path
app/assets/manifest.js
toapp/assets/config/manifest.js
. Avoid the suggestion that you can/should deep-linkstylesheets/foo
.application.js
and.css
. Demonstrate how to uselink_directory
with a specified.js
/.css
type.RAILS_ENV
handling in assets tests.app/assets
toplevel path in Drop toplevelapp/assets
load path sprockets-rails#277