Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 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)

  • Oct 15 20:26

    phillipskevin on master

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

  • Oct 15 20:26
    phillipskevin closed #5372
  • Oct 15 20:25

    phillipskevin on update-make-map

    (compare)

  • Oct 15 20:25
    phillipskevin closed #5381
Justin Meyer
@justinbmeyer
because lets say I requested all items that are "critical" from the server
someone created an issue yesterday
and then labeled it "critical" today
the "created" event shouldn't be fired
however, the instance wouldn't be in the store prior to labeling it "critical"
it existed in the database, it just wasn't in the store
I'm not sure what you mean by set the API domain
Thomas Sieverding
@Bajix
@justinbmeyer My setup looks like api.foo.com, assets.foo.com; I would want my fixtures to be against the domain of my API
I haven’t run into a case in which created was relevant, hence my preference for the upsert approach
Aside from the case of a websocket api broadcasting a created event, usually you wouldn’t be able to know that (outside of save)
Adam L Barrett
@BigAB
Or is this a bug?
Matthew Phillips
@matthewp
@BigAB the callback is a setter, so when you do totalCompute(val) it will be called.
It's not a getter callback
I think this is what you want: https://jsbin.com/yivihecoda/2/edit?js,output
qantourisc
@qantourisc
How does one deal with async loading of can.Components ? Wait until they are loaded before calling can.view ?
Matthew Phillips
@matthewp
Yes
But also, I wouldn't call can.view
I would call stache directly
qantourisc
@qantourisc
Suppose I could also do a {{if windows.comp-name }} but that seems kind of jucky
qantourisc
@qantourisc
Well actually it should be can.view.callback._tags then
Dovid Bleier
@dbleier
my stache all of a sudden stopped rendering. I see console output that the app is running, just no render. Any ideas how to track down what is holding up the render?
Dovid Bleier
@dbleier
I assume it is somehow related to can-wait, but not sure what. This code was working last week
Sunil George
@georgesunil81
A quick question - I developed a simple pagination component that helps paginate results. It is a simple one with Next and Previous buttons and has buttons for individual pages. I am able to use the component fine without any issues, but I want it to sync when I use it on the top and bottom of the page. If I include the component again on the bottom of the page, it is disconnected from the one in the top. I want both pagination components to remain in sync at all times. Anything major that I am missing?
Dovid Bleier
@dbleier
well, at least one thing that seems to be holding this up is this function
    queueNext: function() {
        var self = this,
        ignoredQNR = Zone.ignore(queueNextRec);
        function queueNextRec() {
            self.attr('logger').trace('in queueNext');
            if(self.attr('isplaying')) {
                self.attr('plugin').prepareNext(self.queuedItem().theurl(), self.attr('plugin').Effect.NONE);
                self.attr('plugin').showNow();
                self.play();
                self.attr('playlist').length > 1 && setTimeout(function() {
                    console.log('queueNext ignore setTimeout', self);
                    ignoredQNR();
                },
                self.queuedItem().duration());
            }
        }
        ignoredQNR();

    },
is there something off in the way I am using Zone.ignore?
Kevin Phillips
@phillipskevin
@georgesunil81 you need the components to share a viewModel then
Sunil George
@georgesunil81
Oh, that seems like it. I missed on that. Do you have a link to an example that I can look at?
Kevin Phillips
@phillipskevin
if both components are in the same template, you can share them using a reference scope: https://canjs.com/docs/can.view.bindings.reference.html
Sunil George
@georgesunil81
@phillipskevin do you have an example where components share a viewModel?
Kevin Phillips
@phillipskevin
no
I can make one quickly in JSBin
Sunil George
@georgesunil81
Please if you can. It will be a great help.
Thanks @phillipskevin
Kevin Phillips
@phillipskevin
I’m not actually sure if it’s possible to two-way bind the entire viewmodel to the ref scope
you might have to do individual properties
Matthew Phillips
@matthewp
Can't you do: <some-component *ref ></some-component> ?
Kevin Phillips
@phillipskevin
yeah
but can you do
<some-component *ref ></some-component>
<some-component *ref ></some-component>
that didn’t seem to work for me
Matthew Phillips
@matthewp
two instances?
Kevin Phillips
@phillipskevin
yeah, to sync the viewmodel between the two
Matthew Phillips
@matthewp
oh, so setting the entire view model?
Kevin Phillips
@phillipskevin
right
Matthew Phillips
@matthewp
Hm, it might be possible using the function syntax of can.component
maybe something like this
<some-component *ref ></some-component>
<some-component vm="*ref" ></some-component>