Where communities thrive


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

    greenkeeper[bot] on can-super-model-2.0.0

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

  • 00:13
    greenkeeper[bot] labeled #5448
  • 00:13
    greenkeeper[bot] opened #5448
  • 00:13

    greenkeeper[bot] on can-define-rest-model-2.0.0

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

  • 00:12
    greenkeeper[bot] labeled #5447
  • 00:12
    greenkeeper[bot] opened #5447
  • 00:12

    greenkeeper[bot] on can-define-realtime-rest-model-2.0.0

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

  • 00:07
    greenkeeper[bot] labeled #5446
  • 00:07
    greenkeeper[bot] opened #5446
  • 00:07

    greenkeeper[bot] on can-connect-ndjson-2.0.0

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

  • Dec 13 21:27

    greenkeeper[bot] on @octokit

    (compare)

  • Dec 13 21:25

    greenkeeper[bot] on @octokit

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

  • Dec 13 21:21

    greenkeeper[bot] on @octokit

    (compare)

  • Dec 13 21:20

    greenkeeper[bot] on @octokit

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

  • Dec 12 19:26
    cherifGsoul review_requested #5443
  • Dec 12 18:34
    cherifGsoul synchronize #5443
  • Dec 12 18:34

    cherifGsoul on document-inserted-removed-can6

    Update after review (compare)

  • Dec 12 17:44

    cherifGsoul on theme-3.0.0-pre.5

    (compare)

opolyo01
@opolyo01
does this look right?
if ( ! promiseStore [ key ] ) {
promiseStore[ key ] = $.ajax({
url: can.sub(steal.config('API')[ type ], params, true),
data: params,
type: 'GET',
dataType: 'json',
// work around the ajax bug in chrome
cache: false
});
return promiseStore[ key ];
}
else{
var dfd = $.Deferred();
dfd.promise(promiseStore[ key ]);
dfd.resolve( JSON.parse(promiseStore[ key ].responseText) );
return promiseStore[ key ];
}
dylanrtt
@dylanrtt

@opolyo01 you can probably do it exactly like the QuickCache example. just copy the makeFindAll function out so it's independent and call it like this

var TodoModel = can.Model.extend({
  findTodos: makeCacheable(function(){
    return $.ajax(/*params*/);
  })
}, {});

That should allow you to make any request function cacheable. You can still use it with the standard find methods like this:

var QuickCacheModel = can.Model.extend({
  makeFindAll: makeCacheable
}, {});
Curtis Cummings
@ccummings
I’m trying to create a nested Map that can have children that are the same type. Here’s a jsbin of the setup: http://jsbin.com/peyesififu/1/edit
Depending on what’s defined first I can either have the list be the right type or the map, but not both
dylanrtt
@dylanrtt
@ccummings I had this issue before. Basically one of them needs to be defined before you can reference it in the other. I solved this by modifying the define block of one prototype after declaring both http://jsbin.com/yosakoqozo/1/edit?html,js,console
Curtis Cummings
@ccummings
My brain must be fried. I can also modify the static Map parameter of the list after both are defined
both ways will work. Thanks!
Ilya Fadeev
@ilyavf
hey guys, how can i listen to a list element's property change?
var Row = can.Map({
    define: {
        isChecked: {
            type: 'boolean'
        }
    }
});
var VM = can.Map({
    define: {
        items: {
            Type: Row.List
        }
    }
});
can.Component.extend({
    events: {
        '{scope.items. ??? .isChecked} change': function(){ 
            console.log('item is checked'); 
        }
    }
});
opolyo01
@opolyo01
Hey guys, I am facing an issue where I have 3 Deferreds, and only first one resolves. Other two getting rejected, even though they are all the same deferreds. Any idea?
basically, it is 3 $.ajax deferreds that should have ".then" to have a callback executed, but only first then getting executed. If I do from chrome console it works fine
David Luecke
@daffl
What's the reason for the other Deferreds to get rejected?
Justin Meyer
@justinbmeyer
@ilyavf why are you doing this?
Ilya Fadeev
@ilyavf
@justinbmeyer I have a grid with rows and i need to maintain a hash map of selected rows
opolyo01
@opolyo01
@daffl no idea why is getting reject when I call this from my components
if ( ! promiseStore [ key ] ) {
                promiseStore[ key ] = $.ajax({
                    url: can.sub(steal.config('API')[ type ], params, true),
                    data: params,
                    type: 'GET',
                    dataType: 'json',
                    // work around the ajax bug in chrome
                    cache: false
                });

            }
promiseStore[ key ].then(function(resp){
console.log(resp);
});

return promiseStore[ key ];
Justin Meyer
@justinbmeyer
@ilyavf can you do this w/ a compute instead
opolyo01
@opolyo01
3 components will call this model and I get 3 console.log printed
Justin Meyer
@justinbmeyer
@opolyo01 can you put that in a ```
@patrickclancy regarding model validation ... I would not use our validation plugin
it's probably more simple to use the define plugin
Patrick Clancy
@patrickclancy
@justinbmeyer how would you suggest using the define plugin?
Ilya Fadeev
@ilyavf
@justinbmeyer Like, have a compute property which iterates through my list of items and reads item's property I am interested to listen to?
Patrick Clancy
@patrickclancy
with getters and setters
Justin Meyer
@justinbmeyer
@patrickclancy something like:
define: {
  isNameValid: {
    get: function(){
      return !!this.attr("name")
    }
  }
}
and you could create "mixins" that help set this up
define: validators({}, validateExists("name"))
opolyo01
@opolyo01
@daffl So yeah, promiseStore[ key ].then will be rejected within my components scope, but no while I am in the model. So I wonder would could reject the promise? I know I don't do .reject anywhere
Justin Meyer
@justinbmeyer
@ilyavf yes
do this in the view model
Patrick Clancy
@patrickclancy
@justinbmeyer interesting… I like using the define plugin… everything else is there. I’d need to roll in the check all type functionality that model.errors() provides. But that wouldn’t be hard
Justin Meyer
@justinbmeyer
yeah, the check functionality
is the one thing that this is missing
but in my opinion, having observability
is more important
oh, you mean check all
nm, that can be observable too
I am talking about the "if I set this, will it create an error"
behavior of validations
so you don't actually have to commit a breaking set
to see if there's an error
Patrick Clancy
@patrickclancy
@justinbmeyer is this the direction you’re thinking validation will go? We’ve got models with 60+ fields and observable is important. Bummer I just spent all day doing it the old way
@justinbmeyer I haven’t used this workflow "if I set this, will it create an error”. becasue of can-value live binding. I’d like to integrate that but haven’t
Justin Meyer
@justinbmeyer
yes, validation will certainly be observable
and probably be a plugin into the define plugin itself
if validations are important I can help you create something that bridges the gap
are you using stealjs?
Patrick Clancy
@patrickclancy
yes with ES6 syntax