Load blacklight_range_limit styling via require #1014
Merged
Conversation
This file contains 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
houndci-bot
reviewed
Dec 13, 2017
| @@ -1,2 +1,10 @@ | |||
| /* | |||
| @@ -1 +1,9 @@ | |||
| /* | |||
There was a problem hiding this comment.
Meh, there's a TODO about removing this. I'm not sure if there are any requirements about the comment style and using require, but this is how it was intended to be generated I believe.
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.
We may need to address projectblacklight/blacklight_range_limit#55 upstream to solve this properly but this is temporary solution to get the facet looking correctly in the interim.
Before
After