Use knockout components with CherryTree hiearchial routing
Stars
4
Forks
2
Watchers
4
Open Issues
2
Overall repository health assessment
^3.0.0^5.8.23^3.2.0^1.4.0^2.0.0^0.4.5^0.2.0^0.11.2^8.6.1^2.2.5^3.6.01.9.7-15^6.0.0^1.12.1^2.8.078
commits
Ensure that cherrytree-for-knockout respects other query string variables that change over the lifetime of the view
8912b86View on GitHubMerge pull request #6 from nathanboktae/on-route-transition
d6ab248View on GitHubAdd a mechanism for a parent route to be aware of child transitions
0f84abaView on GitHubresolver function signature was incorrect in the readme
344a2ebView on GitHubExpose a reset function to clear internal state for testing or routing changes
5c53865View on GitHubDispose of view models if requested, just like components
0532d80View on GitHubBig refactor away from knockout components. cherrytree-for-ko needs full control of the bindingContext. Removes the nasty createChildContext monkeypatch hack and asyncronous issues.
c70d859View on GitHub