thats the Object you need to provide thats exactly what a component is
tag + tagData
you can reverse engineer that via console.log(aNormalComponent)
to see some examples
and it would be nice if you could prepare a gist with your results :) so i can use that also
Even better, please consider contributing to the
can-component docs: https://github.com/canjs/can-component/tree/master/docs
@chasenlehara canjs/canjs#3007 wanna look into that?
and maybe writen down your opinion about that?
write lol not writen
i need a way to write proper english my autocorrection don't works well on gitter
It’s the last item we discussed on Friday: http://forums.donejs.com/t/donejs-contributors-meeting-2017-02-10/547/9
there was spoken about generator-donejs
but now i have thrown in that there is a long years existing project that would better fit
and no one commented on that something other then generate a new issue for that and i did that now in CanJS
so out of my view nothing got discussed
For me the result of the last meeting was generator-donejs can be splitted but no one was sure how far and what is donejs what is canjs
and i think this solves all that generator-donejs gets splitted does all donejs related and generator-canjs gets splitted and does all canjs related
I don’t think it’s a priority for the core team until we have more time to think through and discuss what we want to do.
as it also is in use
51 downloads last month :)
If you find value in that project and want to contribute to it, go for it!
I don’t think it’s something the core team has time to put effort into right now.
I am trying to track routes, I want to call google analytics when a route is changed.
I created the following js file..
import can from 'can';
import 'can/map/define/';
import 'can/route/pushstate/';
export default can.Control({
'route': function() {
// Matches every routing change, but gets passed no data.
console.log("Something changed!")
},
':page route': function(data) {
console.log("page change", data);
// Matches routes like #!todos/5,
// and will get passed {id: 5} as data.
},
':page/:item': function(data) {
console.log("page change", data);
// Matches routes like #!recipes/5,
// and will get passed {id: 5, type: 'recipes'} as data.
}
});Then I import it into my app viewModal like this:
import 'app/utils/routing';This doesn't work. I tried putting it on the bottom of the app view model with new Router(window); like this page has https://v2.canjs.com/docs/can.Control.route.html However that also didn't work.
Could someone help me with what I am missing?
all of your route properties will be on your appViewModel already
so you can just use setters there
page: {
set function(val) {
console.log(‘page changed’, val);
return val;
}
}
should be the same as steal 0.16
@phillipskevin It doesn't seem to work for subpages...
page: {
set(newVal) {
if (newVal == 'listing') {
ga('set', { page: newVal + '/' + this.attr("item") , title: this.attr('title') });
ga('send', 'pageview');
} else {
ga('set', { page: newVal, title: this.attr('title') });
ga('send', 'pageview');
}
return newVal;
}
},
However, now this set property make my url domain.com/home/ instead of just domain.com/
if that’s all you need
I don’t think that setter should cause your route to change