Is there any way to use JSON as attribute value in such case:
<my-app my-data="{key: value, key: value}"></my-app>
It doesn't appear in VM if i use this
I can wrap it to quotes, so it will be treated as string, but maybe there is another way
<my-app my-data="key =value key2=value"></my-app>
you could always create a helper / method that would do this too
after update node modules I got
Uncaught ReferenceError: setImmediate is not defined on proto-compute
(because I broke it)
@bmomberger-bitovi tomorrow I have presentation :D
we just need to use the one from can-util
sorry I didn’t catch that before you merged
That's what I was missing.
@bmomberger-bitovi platform you mean node?
This will be quick. I'll let you know as soon as it's out.
thank you
You're welcome. I still have to update can-stache-bindings because I was referencing the broken can-compute there, but that's in process now.
it should get the latest because of semver, right @bmomberger-bitovi ?
Our version specs for anything not
canjs/canjs use ^ which means any patch or minor after the specified one is acceptable.
right, so can-stache-bindings wouldn’t be broken if you re-installed node_modules
I agree it’s still better to update it
it just shouldn’t block @cherifGsoul
NPM versioning mastery is not among my many talents, which is why I rely on my Bitovian colleagues for guidance.
I sorta assumed it was
require-ed
spotted something odd in the docs but when I click on the "Edit on GitHub" link I get a 404: https://github.com/canjs/canjs/edit/master/node_modules/can-define/list/list.js#L894
should point somewhere around here: https://github.com/canjs/can-define/blob/master/list/list.js#L894
can you submit an issue for the broken “Edit on GitHub” link also?
with where you saw it
btw... I'm upgrading to v3.0 and was using
delegate in v2.3. Is this still around or is there some other way to do the same thing?
can I log the issue here?: https://github.com/canjs/can-define/issues/new
logging it there is fine… we can move it if needed
http://canjs.com/doc/can-event.delegate.html is what you’re looking for I think
If you import
can-jquery does that then delegate as expected?
well, I'm trying to remember why I used the delegate since I haven't looked at this code for some time.
I have a suspicion it had to do with route changes that weren't firing correctly when using the
Map directly
the delegate would work as expected
I think that in the handling of the event I was also, at times, changing the route values
instead of
delegate, just us a computed property and listen to when that changes
I'm using define map for the following:
"selection": {
'name': null,
'associated_IDs': [],
get common_associated_IDs() {
return this.name;
},
}but when I set name:
this.default_selectors[selectorIndexNum].set({
selection: {
name: selectorOption.name,
associated_IDs: selectorOption.associated_IDs
}
});and call common_associated_IDs
this.viewModel.default_selectors[0].selection.common_associated_IDs
I still get null
there’s a link at the top of gitter you can use as a starter
Is your first snippet a definition (i.e., is that part of an object you're passing into DefineMap.extend())?
@bmomberger-bitovi yes passing into DefineMap.extend()
OK, so when you want to define a property on a DefineMap as being a DefineMap with its own known properties, then you need to use the
type specifier (or Type), rather than directly giving it property values.
This is documented in http://canjs.com/doc/can-define.types.type.html#_propDefinition_
So your selection property will look like this:
"selection": {
"type": {
'name': { 'value': null },
'associated_IDs': { 'Value': DefineList },
get common_associated_IDs() {
return this.name;
}
}
}
You can tweak the
type and value and getter/setters for each sub-property as needed. They work the same as the containing object, so value is necessary for initial values
If you want the selection to also be initialized, you can then initialize it with
value: {}along with the type def.