Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 19:08
    cherifGsoul labeled #5390
  • 19:07
    cherifGsoul opened #5390
  • 18:45
    greenkeeper[bot] labeled #5389
  • 18:45
    greenkeeper[bot] opened #5389
  • 18:45

    greenkeeper[bot] on can-observable-bindings-1.3.0

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

  • 18:29

    matthewp on master

    Update dist for release (compare)

  • 18:29

    matthewp on v6.1.3

    Update dist for release 6.1.3 (compare)

  • 17:59

    matthewp on can-observable-array-1.0.2

    (compare)

  • 17:59

    matthewp on master

    fix(package): update can-observ… Merge pull request #5388 from c… (compare)

  • 17:59
    matthewp closed #5388
  • 16:46
    greenkeeper[bot] labeled #5388
  • 16:46
    greenkeeper[bot] opened #5388
  • 16:46

    greenkeeper[bot] on can-observable-array-1.0.2

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

  • 12:45
    greenkeeper[bot] labeled #5387
  • 12:45
    greenkeeper[bot] opened #5387
  • 12:45

    greenkeeper[bot] on can-stache-element-1.0.2

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

  • 09:49
    chasenlehara edited #5384
  • 09:47
    chasenlehara edited #3864
  • 09:46
    chasenlehara edited #5383
  • Oct 17 20:12

    matthewp on master

    Update dist for release (compare)

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;
and i swear that worked for about an hour, and then they came back.
Kevin Phillips
@phillipskevin
hmm
Runn Vermel
@runn-vermel
which... ok? weird.
Kevin Phillips
@phillipskevin
depends where you add that I think
Runn Vermel
@runn-vermel
index.js
at my root
Kevin Phillips
@phillipskevin
ok
Runn Vermel
@runn-vermel
at the end of the imports. should i try at the beginning?
ok, that did nothing.
Kevin Phillips
@phillipskevin
first, I would break in can-log inside of warn
and see if this.logLevel is 99
Runn Vermel
@runn-vermel
how do i do that?
Kevin Phillips
@phillipskevin
in chrome devtools, type cmd+p (or ctrl+p for windows)
type in can-log
Runn Vermel
@runn-vermel
(also, i have to get off my bus in about 5 minutes, so, i'll be back later. thanks so much for your help!)
Kevin Phillips
@phillipskevin
find the warn function and click on the line number on the left to add a breakpoint
my guess is you have multiple versions of can-log... and the one you're setting the logLevel on isn't the one we're using
(this isn't a great way of removing the logs)
Runn Vermel
@runn-vermel
oh! i'm open to the best way ;)
Kevin Phillips
@phillipskevin
well... there isn't really a best way... other than fixing them
Runn Vermel
@runn-vermel
you can understand why i don't have time to fix a super old app that's being replaced ;)
Kevin Phillips
@phillipskevin
I do understand, yeah
I definitely get that it's annoying... I just don't have a better answer for you right now