Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Oct 17 20:12

    matthewp on master

    Update dist for release (compare)

  • Oct 17 20:12

    matthewp on v6.1.2

    Update dist for release 6.1.2 (compare)

  • Oct 17 20:04

    matthewp on master

    Update dist for release (compare)

  • Oct 17 20:04

    matthewp on v6.1.2-0

    Update dist for release 6.1.2-0 (compare)

  • Oct 17 19:17
    akbaruddin starred canjs/canjs
  • Oct 17 17:25
    matthewp edited #5384
  • Oct 17 17:00

    matthewp on can-dom-mutate-2.0.7

    (compare)

  • Oct 17 17:00

    matthewp on master

    fix(package): update can-dom-mu… Merge pull request #5386 from c… (compare)

  • Oct 17 17:00
    matthewp closed #5386
  • Oct 17 16:27
    greenkeeper[bot] labeled #5386
  • Oct 17 16:27
    greenkeeper[bot] opened #5386
  • Oct 17 16:27

    greenkeeper[bot] on can-dom-mutate-2.0.7

    fix(package): update can-dom-mu… (compare)

  • Oct 17 16:25

    matthewp on can-dom-mutate-2.0.6

    (compare)

  • Oct 17 16:24
    matthewp closed #5379
  • Oct 17 16:24
    matthewp commented #5379
  • Oct 17 15:26

    greenkeeper[bot] on can-type-1.1.2

    (compare)

  • Oct 17 15:26

    matthewp on master

    fix(package): update can-type t… Merge pull request #5385 from c… (compare)

  • Oct 17 15:26
    matthewp closed #5385
  • Oct 17 14:11
    matthewp closed #5377
  • Oct 17 14:11
    matthewp closed #5376
Gregg Roemhildt
@roemhildtg
canjs/can-define#309
Gregg Roemhildt
@roemhildtg
Anyone ever created a "batch save" method in can-connect? Instead of model.save(oneItem) saving multiple items in one requestmodel.save([item1, item2, item3]);?
I gotta create about a thousand records in one go...and I think calling .save x1000 would not be pretty
feathersClient accepts an array of data though...so maybe a custom behavior with a special function like saveBatch would be the way to go.
sound about right?
Nico R.
@nriesco
@roemhildtg the Potentially unhandled rejecttion … object is not extensible error occurs when that variable is not defined in the viewmodel
usually happens when you are trying to get a property from the wrong place
Kevin Phillips
@phillipskevin
the problem he is pointing out is that _instanceDefinitions is not the name of the property that is being set
Nico R.
@nriesco
or you just forgot to define it, I think the difficutly is that it only occurs when trying to save or when you don’t load an inital content
Oh, I see
Gregg Roemhildt
@roemhildtg
Hey, calling a definMap.get should return all its properties, right? Even if serialize:false is set on a property?
Or does serialize: false affect .get() as well as .serialize()?
Kevin Phillips
@phillipskevin
get also just returns enumerable properties
Runn Vermel
@runn-vermel
@phillipskevin - the problem is that i can't data bind it - long story. there's something that's preventing the select from knwoing there's been a change in the option selected. i know (vaguely) that canJs has something that adds a value property to a select - but that doesn't seem to get updated. it knows there's a change, but the value on the select doesn't change, so i was hoping that maybe there's a way to access the change event that is generated with the ($change) function call
Gregg Roemhildt
@roemhildtg
Okay gotcha.
Kevin Phillips
@phillipskevin
<select> has value without CanJS
Runn Vermel
@runn-vermel
@phillipskevin i humbly disagree: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/select - it has selectedIndex but no value.
that's why I tried it in the JSBin... because it wasn't readily available on the docs you pointed out
it's in the DOM Interface link though
Runn Vermel
@runn-vermel
ha - thanks MDN. 2 docs for the same thing with different attributes on them. either way, value isn't being updated when i make a new selection... any ideas?
Kevin Phillips
@phillipskevin
the value isn't? or the property you're binding it to isn't?
Runn Vermel
@runn-vermel
the value isn't
i can't bind to a property because of how the data is structured.
so, i just wanna be notified when there's a change, and check for the (hopefully) changed value, and act accordingly
Kevin Phillips
@phillipskevin
  <select class="form-control"
          {($value)}="trainsByPlatform[platform.name]"
          ($change)="upsertInitialRelease(platform.name, scope.element.value)">
    <option></option>
    {{#each trains[platform.name] as train}}
    <option value="{{train.name}}">{{train.name}}</option>
    {{/each}}
  </select>
is that the code you have?
Runn Vermel
@runn-vermel
yup
Kevin Phillips
@phillipskevin
and you're saying that upsertInitialRelease isn't being called?
Runn Vermel
@runn-vermel
it is, but scope.element.value is NEVER changed
Kevin Phillips
@phillipskevin
ok
so... I would first change {($value)} to be only one-way bound
{$value}
so you only have one handler element->viewModel and one handler viewModel->element
right now you have a two-way binding and a one-way binding
Runn Vermel
@runn-vermel
at first we thought perhaps it was a timing issue - but it NEVER changes, and the select doesn't actaully show the new option - it always stays at the empty first option
Kevin Phillips
@phillipskevin
did you try changing it to
          {$value}="trainsByPlatform[platform.name]"
          ($change)="upsertInitialRelease(platform.name, scope.element.value)">
Runn Vermel
@runn-vermel
OMG. that was... simple. of course - doing it 1 way means it can update itself...
Kevin Phillips
@phillipskevin
oh, that was it?
Runn Vermel
@runn-vermel
i'm reloading, just to be sure :)
yes, that was totally it. big sigh of relief
Kevin Phillips
@phillipskevin
ok cool. maybe we should warn if you have multiple of the same binding. I don't know if that would ever be something you want.
Runn Vermel
@runn-vermel
lol.
ok, since i got your attention (your awesome), those warnings are back. i have 100s of them
Kevin Phillips
@phillipskevin
which warnings specifically?
Runn Vermel
@runn-vermel
%index is deprecated. Use scope.index instead.
whoa, that's not it. sorry
can-stache-bindings: the event binding format ($click) is deprecated. Use on:click instead