Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Oct 22 20:11

    matthewp on master

    Update dist for release (compare)

  • Oct 22 20:11

    matthewp on v6.2.0

    Update dist for release 6.2.0 (compare)

  • Oct 22 20:05

    matthewp on master

    Fix bundlesize (compare)

  • Oct 22 19:22

    matthewp on can-observable-bindings-1.3.0

    (compare)

  • Oct 22 19:22

    matthewp on master

    fix(package): update can-observ… Set new bundle sizes Merge pull request #5389 from c… (compare)

  • Oct 22 19:22
    matthewp closed #5389
  • Oct 22 19:09
    matthewp commented #5389
  • Oct 22 18:33

    matthewp on can-attribute-observable-2.0.1

    (compare)

  • Oct 22 18:33

    matthewp on master

    fix(package): update can-attrib… Increase the bundlesize Merge pull request #5394 from c… (compare)

  • Oct 22 18:33
    matthewp closed #5394
  • Oct 22 17:59
    matthewp synchronize #5394
  • Oct 22 17:59

    matthewp on can-attribute-observable-2.0.1

    Increase the bundlesize (compare)

  • Oct 22 17:42
    matthewp synchronize #5389
  • Oct 22 17:42

    matthewp on can-observable-bindings-1.3.0

    fix(package): update can-observ… Set new bundle sizes (compare)

  • Oct 22 17:26
    greenkeeper[bot] labeled #5394
  • Oct 22 17:26
    greenkeeper[bot] opened #5394
  • Oct 22 17:26

    greenkeeper[bot] on can-attribute-observable-2.0.1

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

  • Oct 22 17:15

    matthewp on can-stache-element-1.0.2

    (compare)

  • Oct 22 17:15

    matthewp on master

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

  • Oct 22 17:15
    matthewp closed #5387
Frank Lemanschik
@frank-dspeed
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!!
Kevin Phillips
@phillipskevin
yep, no problem
RyanMilligan
@RyanMilligan
We have kind of an unusual scenario for updating lists that real-time doesn't seem to handle properly. We worked around it in the past by forking can-connect and fixing the issue, but now that we're on Can 3 we're hoping to move away from that.
Basically, we have a number of pages where we display a join of two (or more) tables, where each row represents a combination of those joined tables and may or may not be backed by an actual database row; the middle tier returns all possible combinations, and the ones that don't exist have a null id.
This works fine in general, but when the user deletes a row, everything goes haywire. The middle tier returns {id: null} in the payload, the original object's id gets nulled out...but then in real-time.js, indexOf(self, props, list) returns whatever happens to be the first index in the list that doesn't have an id, and it overwrites the wrong object. The end result is that an essentially random row disappears and the row they deleted gets duplicated.