Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Sep 20 21:04
    m-mujica commented #5303
  • Sep 20 20:23
    m-mujica opened #5303
  • Sep 20 20:23

    m-mujica on upgrade-deps

    Update can-type and can-stache-… (compare)

  • Sep 20 20:05
    m-mujica edited #5302
  • Sep 20 20:03
    m-mujica synchronize #5302
  • Sep 20 20:03

    m-mujica on upgrade

    Upgrade routing guide to Can 6 Fix incorrect highlight Use svg images (instead of .png) (compare)

  • Sep 20 19:32
    m-mujica opened #5302
  • Sep 20 19:29

    m-mujica on upgrade

    Upgrade routing guide to Can 6 Fix incorrect highlight (compare)

  • Sep 20 17:42

    m-mujica on upgrade

    WIP: Upgrade (compare)

  • Sep 20 17:06
    do-adams starred canjs/canjs
  • Sep 20 13:34

    chasenlehara on 5119-testing-guide

    Update the Testing guide for Ca… (compare)

  • Sep 20 13:21
    cherifGsoul commented #5295
  • Sep 20 13:18
    cherifGsoul synchronize #5295
  • Sep 20 13:18

    cherifGsoul on update-theme-new-buttons

    Theme pre-release 2 (compare)

  • Sep 20 10:29

    greenkeeper[bot] on socket.io-client-2.3.0

    (compare)

  • Sep 20 10:26

    greenkeeper[bot] on socket.io-client-2.3.0

    chore(package): update socket.i… (compare)

  • Sep 20 06:40
    HellMagic starred canjs/canjs
  • Sep 19 20:42
    m-mujica commented #5119
  • Sep 19 18:40
    phillipskevin closed #5300
  • Sep 19 18:40
    phillipskevin commented #5300
Frank Lemanschik
@frank-dspeed
: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
@frank-dspeed would that work with canjs 3? any shareable code? :-)
Frank Lemanschik
@frank-dspeed
feathers 3 will work with can 3 but its more hard to debug then
at present i have it running in some diffrent ways
but the most importent info is maybe that can-connect-feathers v2
even still works
i think the warning that it don't works comes from the new feathers 3 channel integration part
if your using feathers3 server side you need to let it handle where to publish updates
  app.on('connection', connection => {
    // On a new real-time connection, add it to the anonymous channel
    app.channel('anonymous').join(connection);
  });
  // Lets publish to anyone at present
  app.publish(() => {    app.channel('anonymous');  });
so this 2 things need to get added to get the old canjs behaviers working out of the box
as this makes sure that every connected client joins a channel called anonymous
and all in channel anonymouse get all update created removed events
as it was befor
this was the default behavior of feathers 2
Frank Lemanschik
@frank-dspeed
and about the ssr socket.io part
i used can-zone Zone(io)
it ignores can zone
but works
Runn Vermel
@runn-vermel
@nriesco yeah, making it one way bind allowed the change to be reflected in the UI - that's all i did.
@phillipskevin ok, i have a new issue now: inside can-define/define-helpers/define-helpers.js Chrome dev tools has paused with the following message: "Paused before potential out-of-memory crash" - it paused on map.each call on line 126
the array it's mapping through only has 130 items, so, not huge.
@justinbmeyer ^ any ideas?
Kevin Phillips
@phillipskevin
@nriesco it is really two one-way binds
          {$value}="trainsByPlatform[platform.name]"
          ($change)="upsertInitialRelease(platform.name, scope.element.value)">
one-way binding in each direction
@runn-vermel can you send a link to the line in the code?
Justin Meyer
@justinbmeyer
nope, that should be ok ... maybe possible recursion, an item that has itself
Runn Vermel
@runn-vermel
Hi @phillipskevin - i wish i could, but sadly, i can't. it's this function:
This message was deleted
`` map.each(function (val, name) { // If the value is anobject, and has anattrorserialize` function.
            var result,
                isObservable =   hasMethod(val, how),
                serialized = isObservable && serializeMap[how][CID(val)];

            if( serialized ) {
                result = serialized;
            } else {
                // special attr or serializer
                result = defineHelpers.getValue(map, name, val, how);
            }
            // this is probably removable
            if(result !== undefined) {
                where[name] = result;
            }


        });```
inside the serialize method on that page
Kevin Phillips
@phillipskevin
ok, are you on an older version of can-define?
looks like that code was refactored recently
Runn Vermel
@runn-vermel
let me check what i got.
i'm on 1.2.0
looks like the latest one is 1.5.3
Kevin Phillips
@phillipskevin
any reason you can't update?
Runn Vermel
@runn-vermel
but... i have to admit, i'm super scared to update anything fromthe canJs packages. trouble seems to follow doing that. ha.
i'll do it locally now and see if fixes it, or causes anything else..
Kevin Phillips
@phillipskevin
never want to hear that, hope it goes ok
Runn Vermel
@runn-vermel
thanks. i don't mean to be offensive (at all), and i really appreciate all your help with this.
i'm running into all these issues because after not touching the app in production for a while, we had to do an update, which pulled in new packages - we had ^ in our canJS packages. and... now we have these issues.
Kevin Phillips
@phillipskevin
yeah, no offense taken
Runn Vermel
@runn-vermel
@phillipskevin - ok, i updated and locally it looks good. it's on our staging server, and seems to be running better, so let's hope that was it :) thanks again!!