active.set now sets the active page, and it accepts
an element, instead of an id. This lets us navigate
even when we have many pages of the same id open.
Split navigation code into lib/active.coffee
Does that mean it will stop jumping back to the first open copy of a page if I try to open the page again further along my meanderings?
I rather liked that behaviour.
Yeah. Unfortunately we discovered that it was useful to have sets of pages up with multiples of the same page, and be able to navigate them normally.
Rearranged fetch some more, added tests.
Moved wiki.fetchContext to fetch.context, rearranged fetch so that the logic as to what to call buildPage with is all in the main function, and added tests.
I've been cheating some with a faked up wiki object in these tests, hoping to quit when we get the main api into it's own module.