- #95 - keeping the already defined handler of
onhashchange
- A path because of the latest release. It covers the case where we are using a custom hash. #92
- Fixing #87
- Make sure we have a function when using named routes #86 (by Tobias Nyholm (@Nyholm))
- Support of custom hash string like
#!
for example. Read the docs for more information.
- Fixing #82.
- Adding
off
API method #72.
- Fixing #77.
That's a minor but a breaking change. The generate
method now outputs proper strings base on the useHash
parameter. Or in other words if the router is using hash based routing the generated URLs contain #
in the beginning.
- Proper initialization of the root when using
useHash = true
- Minor fix while resolving hash based URLs (for Firefox)
- Adding a
resume
method which is same as.pause(false)
..pause
now acts as.pause(true)
by default.
- Fixing #63.
- Support of hooks in named routes. (#60)
- Merging #58 where we can prevent the handler calling from a before hook.
- Another try fixing #57 - now if we have
noHash=false
the hash part of the URL is removed and we are no longer considering it while comparing the last resolved URL.
- Fixing #57 - making sure that we keep the last resolved url when we have the
notFound
handler resolves.
- Fixing #56 - When a
/
is given as a path it is considered as a default route handler.
- Start using
onhaschange
API as a default for hash based routing. - Using karma as a test runner.
- Fixing the case where route handlers are not fired when only the query string part of the URL is changed (#53)
- hooks support.