This repository has been archived by the owner on Dec 30, 2022. It is now read-only.
fix(RangeInput): make the header slot valid #406
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
rayrutjes
approved these changes
Mar 15, 2018
|
Not sure why it broke, but I saw that this was the only difference between RangeInput and PriceRanges w.r.t. slots and this one didn't work, while the other one did |
|
For me this only changes something if one tries to directly use the component in the browser instead of using UMD or compiling with the vue compiler. I might be wrong though :) |
|
Thought to too, but I don't understand why else that codeSandbox was behaving like it was |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
fixes #405