sending wildcards to the viewmodel with requireVM

[maxfridbe]

I am following the common requieVM pattern and am having an issue accessing the property set.

<div class="viewServer" data-bind="page:{id:'viewServer'}" >
                <div data-bind="page:{id:'?', nameParam:'Address', sourceOnShow:'/views/servers/viewServer.html', withOnShow:requireVM('/viewmodels/servers/viewServerViewModel.js')}">

                </div>
            </div><!--END PAGE-->

This hit's twice in pagerjs:

 if (this.ctx[nameParam]) { // set observable ...
                            this.ctx[nameParam](this.currentId);
                        } else { // ... or create observable
                            this.ctx[nameParam] = ko.observable(this.currentId);
                        }

First it creates a new observable because context is not set.
Then it sets the observable.

In the VM doing:

 self.Address.subscribe(function(newval){
            alert(self.Address());
        });

Does nothing, as the self.Address gets overwritten.

When trying to get to #/viewserver/ipaddress

[finnsson]

Thanks for the bug report.

I have limited time to check for the solution at the moment. I guess pagerjs need to defer the creation/binding of currentId until the view model is loaded or maybe merge the created observables with the lazy-loaded view-model somehow.

A workaround until I've fixed this might be to use bind (undocumented feature at the moment) that can be used like

var viewModel = {
  myPage: ko.observable()
};

<div data-bind="page: {id: 'foo', bind: myPage}"></div>

where the pager.Page-object will be bound to the observable myPage. From there you should be able to fetch the currentId (you can use getCurrentId which is an observable to the current ID).

Another tip is to use navigationFailed (http://pagerjs.com/demo/#!/navigation/failed_navigation) to create child-pages on-demand instead of using id: '?'. There are some trade-offs between the different solutions (using navigationFailed makes it possible to animate between page transitions - on the downside new dom-elements are created and the code is at the moment a bit more verbose).

Hope this helps.