If you mean in your JavaScript or (S)CSS "application" pages, that's because there's no other mechanism that a gem could use to auto-mount the paths there. The Bootstrap gem is essentially just providing packaging for the JS and CSS that is Bootstrap. That last few inches is you adding it to your application in a thoughtful way, just as you would any other JS or (S)CSS file.
If there were an "automatic" way to add it, it would probably be like the CSS ` *= require_tree .` construct, which works alphabetically. That would ignore any overrides you wanted to set, or in the case of SCSS, any variables you wanted to populate with values. Doing things the long-hand way gives you a chance to ensure that requirements are met and there's a predictable order to loading. The same sort of thing would be even more critical in JS, where alphabetical order might load a jQuery plugin before jQuery itself. Walter > On Sep 20, 2019, at 8:42 AM, fugee ohu <[email protected]> wrote: > > ? > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/rubyonrails-talk/24df8def-a4da-4459-bdfa-f1b4d3a02812%40googlegroups.com. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/D99660F1-8F1D-4B21-883B-14DD382A670E%40wdstudio.com.
