Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 00:14
    greenkeeper[bot] labeled #5449
  • 00:14
    greenkeeper[bot] opened #5449
  • 00:14

    greenkeeper[bot] on can-super-model-2.0.0

    fix(package): update can-super-… (compare)

  • 00:13
    greenkeeper[bot] labeled #5448
  • 00:13
    greenkeeper[bot] opened #5448
  • 00:13

    greenkeeper[bot] on can-define-rest-model-2.0.0

    fix(package): update can-define… (compare)

  • 00:12
    greenkeeper[bot] labeled #5447
  • 00:12
    greenkeeper[bot] opened #5447
  • 00:12

    greenkeeper[bot] on can-define-realtime-rest-model-2.0.0

    fix(package): update can-define… (compare)

  • 00:07
    greenkeeper[bot] labeled #5446
  • 00:07
    greenkeeper[bot] opened #5446
  • 00:07

    greenkeeper[bot] on can-connect-ndjson-2.0.0

    fix(package): update can-connec… (compare)

  • Dec 13 21:27

    greenkeeper[bot] on @octokit

    (compare)

  • Dec 13 21:25

    greenkeeper[bot] on @octokit

    chore(package): update @octokit… (compare)

  • Dec 13 21:21

    greenkeeper[bot] on @octokit

    (compare)

  • Dec 13 21:20

    greenkeeper[bot] on @octokit

    chore(package): update @octokit… (compare)

  • Dec 12 19:26
    cherifGsoul review_requested #5443
  • Dec 12 18:34
    cherifGsoul synchronize #5443
  • Dec 12 18:34

    cherifGsoul on document-inserted-removed-can6

    Update after review (compare)

  • Dec 12 17:44

    cherifGsoul on theme-3.0.0-pre.5

    (compare)

Nico R.
@nriesco
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
Kevin Phillips
@phillipskevin
oh, yeah, those are deprecated
(and removed in 4.0, which will be released very soon)
Runn Vermel
@runn-vermel
yeah. so is this app - we are building a now one - i don't want to go through and change things - just turn of the 100s of warnings i'm getting...
Runn Vermel
@runn-vermel
i added this:
import CanLog from "can-log";
CanLog.logLevel = 99;