failing test case with .html.erb preferred instead of .coffee #121
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
|
since this is no solution for the problem, I would ask how and where this problem should be fixed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR shows coffee-rails views not being picked for JS routes when a .html.erb template exists for the same action.
In the comments of the dummy controller are the currently necessary steps (I haven't found explicit documentation about needing to do this!) to make the
.coffeefile (or.js.coffee) being picked up and served when accessing/site/index.js.NOTE: the current full test suite fails (even without these changes) since sprockets 4.0 will be installed and it requires a set up manifest.js for the asset pipeline...