Documenting custom elements #371
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
|
Thanks! I'd like to review within a week. |
| @@ -0,0 +1,80 @@ | |||
| <h1><{{name}}></h1> | |||
There was a problem hiding this comment.
Good spot, I'll fix this shortly!
|
It looks great to me, and I feel that it needs to update user guide for this. |
|
I just tweaked docs. |
Update docs on supporting Custom Elements
|
I've merged this. I'm planning to release the next version in this week. This feature will be available in the next version. Thanks your great contributions. 👍 |
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.
This covers the requirements laid out in #328 by providing a new top-level
@elementtag, as well as adding subtags@parents,@contentand@interface.@example,@deprecated, etc{{#crossLink <x-foo attr>}}Please review and let me know if there's anything I've missed or overlooked.