Where communities thrive


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

    greenkeeper[bot] on can-simple-map-4.3.3

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

  • Oct 14 20:19
    greenkeeper[bot] labeled #5377
  • Oct 14 20:19
    greenkeeper[bot] opened #5377
  • Oct 14 20:19

    greenkeeper[bot] on @feathersjs

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

  • Oct 14 20:18
    greenkeeper[bot] labeled #5376
  • Oct 14 20:18
    greenkeeper[bot] opened #5376
  • Oct 14 20:18

    greenkeeper[bot] on @feathersjs

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

  • Oct 14 14:43
    greenkeeper[bot] closed #5373
  • Oct 14 14:43

    greenkeeper[bot] on can-deep-observable-1.0.1

    (compare)

  • Oct 14 14:42

    m-mujica on update-deep-observable

    (compare)

  • Oct 14 14:42

    m-mujica on master

    Update can-deep-observable to l… Merge pull request #5374 from c… (compare)

  • Oct 14 14:42
    m-mujica closed #5374
  • Oct 14 14:42
    m-mujica closed #5365
  • Oct 14 14:09
    f-ricci starred canjs/canjs
  • Oct 14 13:55
    greenkeeper[bot] commented #5375
  • Oct 14 13:55

    greenkeeper[bot] on core-js-3.3.2

    chore(package): update core-js … (compare)

  • Oct 14 10:51
    m-mujica review_requested #5374
  • Oct 14 07:43
    rjgotten commented #5358
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
Frank Lemanschik
@frank-dspeed
@kevin this migration guide is like gold :)
it should get more highlighted
:D
but good to know that canJs was intuitiv enough for me already to get it rendering i am happy with can4
i also got feathers 3 working maybe just finishing the last tests
and test all situations but it looks that socketio 2 with feathers 3 is working with ssr
CanJS 4's is really epic because of the great automount concept using webcomponents i hope we get webcomponents stuff into canjs 5 even more
so that canjs is simply the better polymer
Nico R.
@nriesco
@runn-vermel @phillipskevin I’m confused with the select issue, was it solved with one way binding? If that is the case, it won’t work for me because I use it both to set the value when selecting and to load the initial value. Is that possible using your solution? @runn-vermel can you share the code? thanks