Adding clarity around using JSON in attributes #15
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
Add note to let users know html encoded strings are required to be passed in for arrays etc
Update README.md
This reverts commit 93266ed.
Feature/dynamic dom
|
Closing this one as it will now be released in v0.5.0 instead |
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.
Hey guys,
Can you please have a read of our updated read me and provide any feedback. Its a hard concept to explain but please have a read of the "Use encoded JSON in HTML attributes" section.
This is to help solve issues such as #11
I've also made some other read me heading tweaks, added yarn install to the instructions given its popularity and updated the example packages.
Thanks
J