Remove isolate_namespace to fix unresolved split_stylesheet_link_tag #66
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I added what seemed to be a completely unrelated gem and began getting undefined method `split_stylesheet_link_tag' as described in #45. I tried the fix recommended in the comments of removing the isolate_namespace and that resolved things for me.
I'm not sure what caused it in my case but I noticed that before including the unrelated gem, css_splitter would get included as a helper before my local helpers. After including the unrelated gem, it would get included after but it wouldn't be in my ancestor chain when loading the view. Thats as far as I got trying to figure out what was going on.