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.

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

move code back into virtual-dom #118

Merged
merged 5 commits into from
Nov 17, 2014
Merged

Conversation

Raynos
Copy link
Collaborator

@Raynos Raynos commented Nov 17, 2014

This is a PR that moves vtree, vdom & virtual-hyperscript back
into virtual-dom so that we can have all the issues and
communication happening in one place.

This also solves pain points with versioning.

cc @Matt-Esch

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 800f41c on Raynos:all-in-one into * on Matt-Esch:master*.

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 0d261da on Raynos:all-in-one into * on Matt-Esch:master*.

@staltz
Copy link
Contributor

staltz commented Nov 17, 2014

Yes please thanks, I was getting tired of flipping aroung between repos.

assert.equal(rootNode.value, "")
assert.end()
})

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why was this test removed?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

difference in semantics between old h & virtual-hyperscript.

@neonstalwart
Copy link
Collaborator

👏 much less npm linkage when fixing bugs.

@Raynos
Copy link
Collaborator Author

Raynos commented Nov 17, 2014

@Matt-Esch Matt-Esch merged commit 0d261da into Matt-Esch:master Nov 17, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants