GHCJS.VDOM.Unsafe: exporting js_vnode and internal javascript references... #7
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
…ces for Properties, Children, Patch and VNode
|
Seems like a good alternative to my patch. |
|
Your idea here is that the Unsafe module is for custom stuff and the standard module only exports smart constructors for known elements? I like the idea. I'm OK with merging. @luite thoughts? |
|
Yes. In addition, it is often needed to use |
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.
... for Properties, Children, Patch and VNode
I exported those to make use of ghcjs-vdom for webcomponent custom element (such as Polymer elements). This issue was discussed in #6 and #3.