Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Oct 16 20:07
    matthewp commented #5384
  • Oct 16 20:06
    matthewp labeled #5384
  • Oct 16 20:06
    matthewp opened #5384
  • Oct 16 19:53
    matthewp opened #5383
  • Oct 16 16:23
    phillipskevin closed #4841
  • Oct 15 21:43

    phillipskevin on master

    Update dist for release (compare)

  • Oct 15 21:43

    phillipskevin on v6.1.1

    Update dist for release 6.1.1 (compare)

  • Oct 15 21:34

    phillipskevin on can-observable-mixin-1.0.2

    (compare)

  • Oct 15 21:34

    phillipskevin on master

    fix(package): update can-observ… Merge branch 'master' into gree… Merge pull request #5382 from c… (compare)

  • Oct 15 21:34
    phillipskevin closed #5382
  • Oct 15 21:34

    phillipskevin on can-make-map-1.2.2

    (compare)

  • Oct 15 21:34

    phillipskevin on master

    fix(package): update can-make-m… Merge pull request #5380 from c… (compare)

  • Oct 15 21:34
    phillipskevin closed #5380
  • Oct 15 20:30
    phillipskevin synchronize #5382
  • Oct 15 20:30

    phillipskevin on can-observable-mixin-1.0.2

    fix(package): update can-observ… fix(package): update can-simple… Merge pull request #5372 from c… and 2 more (compare)

  • Oct 15 20:30
    phillipskevin opened #5382
  • Oct 15 20:28

    phillipskevin on can-simple-map-4.3.3

    (compare)

  • Oct 15 20:28

    phillipskevin on master

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

  • Oct 15 20:28
    phillipskevin closed #5378
  • Oct 15 20:26

    phillipskevin on can-observable-mixin-1.0.1

    (compare)

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
Runn Vermel
@runn-vermel
you're right - this.logLevel returned 0
totally.
Kevin Phillips
@phillipskevin
npm ls can-log
try to match your version with whatever version your can-* dependencies are using
so there is only one
Runn Vermel
@runn-vermel
│ ├─┬ can-stache-key@0.1.3
│ │ └── can-log@0.1.2  deduped
│ ├─┬ can-types@1.1.5
│ │ └── can-log@0.1.2  deduped
│ └─┬ can-view-scope@3.5.5
│   └── can-log@0.1.2  deduped
├── can-log@0.1.2 
├─┬ can-route@3.3.2
│ └── can-log@0.1.2  deduped
├─┬ can-stache@3.14.8
│ ├─┬ can-attribute-encoder@0.3.3
│ │ └── can-log@0.1.2  deduped
│ ├── can-log@0.1.2  deduped
│ └─┬ can-view-parser@3.8.0
│   └── can-log@0.1.2  deduped
├─┬ can-stache-bindings@3.11.9
│ └── can-log@0.1.2  deduped
├─┬ can-util@3.11.0
│ └── can-log@0.1.2  deduped
└─┬ steal-stache@3.0.5
  └─┬ can-view-import@3.2.7
    └── can-log@0.1.2  deduped
ok, getting off the bus - have no idea how to change it to only one - it seems like they are all using the same version though
Kevin Phillips
@phillipskevin
ok, yeah, that looks fine
so... you need to make your CanLog.logLevel = 99; run earlier