Update to support original element values #14
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
My use case is: <input type="tags" value="tag1, tag2"> and I'd expect to see the following displayed tag1 tag2 This patch falls back to the original element's value and supports the use case.
|
@tbranyen Awesome, thanks! No problem with the generated files, I think this is my only repo that includes them in SCM. |
|
Released in 1.1.0. |
|
Awesome thanks for the quick turnaround @developit! |
zaygraveyard
pushed a commit
to zaygraveyard/tags-input
that referenced
this pull request
Jan 26, 2017
support browser field
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.
My use case is:
and I'd expect to see the following displayed
This patch falls back to the original element's value and supports the
use case.
Note: I did not commit the generated files. Let me know and I'll add them as a separate commit.