Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Should support components? #5

Closed
himalayafan opened this issue Oct 22, 2015 · 1 comment
Closed

Should support components? #5

himalayafan opened this issue Oct 22, 2015 · 1 comment

Comments

@himalayafan
Copy link

A must this days is components, and if Himalaya should be used with virtual DOM libraries, I suggest you add in support for components. Now you have a Text, Element, Comment node.

What about adding in a 4th node? Component? I think that will drag users to this script.
@himalayafan himalayafan mentioned this issue Oct 22, 2015
Closed
@andrejewski
Copy link
Owner

Himalaya is used to parse HTML into a JSON representation of that HTML. Components are an abstraction provided by vdoms that are not actually apart of the HTML. Himalaya aims to be one-to-one with the HTML, not the higher abstraction. If someone needs a new node they can build on top of the spec to meet their needs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@andrejewski @himalayafan