Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 16:40

    cherifGsoul on update-api-page

    (compare)

  • 16:39

    cherifGsoul on master

    Update API page (#5432) * Upda… (compare)

  • 16:39
    cherifGsoul closed #5432
  • 16:39
    cherifGsoul closed #5304
  • 01:04
    greenkeeper[bot] commented #5392
  • 01:04

    greenkeeper[bot] on core-js-3.5.0

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

  • Dec 11 18:34
    greenkeeper[bot] labeled #5444
  • Dec 11 18:34
    greenkeeper[bot] opened #5444
  • Dec 11 18:34

    greenkeeper[bot] on can-observable-mixin-1.0.7

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

  • Dec 11 18:30

    cherifGsoul on update-infrastructure-page

    (compare)

  • Dec 11 18:30

    cherifGsoul on master

    Update infrastructure page with… (compare)

  • Dec 11 18:30
    cherifGsoul closed #5441
  • Dec 11 18:30
    cherifGsoul closed #5417
  • Dec 10 17:40
    cherifGsoul review_requested #5443
  • Dec 10 16:47
    cherifGsoul review_requested #5441
  • Dec 10 16:35
    cherifGsoul synchronize #5441
  • Dec 10 16:35

    cherifGsoul on update-infrastructure-page

    Fix typos (compare)

  • Dec 10 10:01
    jkeruzec starred canjs/canjs
  • Dec 09 18:59
    cherifGsoul review_requested #5443
  • Dec 09 18:59
    cherifGsoul opened #5443
Justin Meyer
@justinbmeyer
I generally don't write code like that
Matthew Phillips
@matthewp
it's from that forum post, not sure if you wrote it or @jeroencornelissen did
Frank Lemanschik
@frank-dspeed

@justinbmeyer suggested this on the gitter channel:

I would put a destroyList or some method on your list that makes the requests
and then call destroyedInstance on each one (assuming can-connect)

I have tried that but couldn’t make it work. The items are updated when calling Item.Connection.destroyedInstance(item, {title: 'destroyed'});. The title changes to destroyed, but I expected them to get removed from the list.

See this fiddle 3:

ah ok
it was gregromhild
sorry
:D
readed it wrong i tought he copyed your text
Justin Meyer
@justinbmeyer
I remember giving code IN gitter, I wish there was a link to the gitter thread
Frank Lemanschik
@frank-dspeed
if you got gitter pro
you should be able to find it
do you got a pro account?
it has infinity history and search
as far as i remember
Justin Meyer
@justinbmeyer
basically, the .save() on a list would need to update the instances correctly
there's a way to do that
Frank Lemanschik
@frank-dspeed
dispatch
Justin Meyer
@justinbmeyer
it's not dispatch
(though a dispatch happens)
I'd look it up but in the middle of something
Frank Lemanschik
@frank-dspeed
i saw in some examples that there was custom dispatch on stuff like
can-define backup
thats why i got that idea
Justin Meyer
@justinbmeyer
essentially you would need to re-create what the normal .save() does on every item in the list
Frank Lemanschik
@frank-dspeed
thats correct
it will call some defineMap methods
maybe set ? update somestuff like that
i use that methods when i don't use can connect
to directly update instances
or save maybe as i remember uses the methods
added by can connect
!
this are the right api's i think to tigger updates
the crud methods
Mike 'mitch' Mitchel
@mikemitchel
added the .sort method back to can-list 4.2.0
https://github.com/canjs/can-list/releases/tag/v4.2.0
kostya.aderiho
@kaderiho
according to your comments @frank-dspeed @justinbmeyer I need to write custom implementation updateListData in order to send one PUT request with list inside of body?
Frank Lemanschik
@frank-dspeed
right
@kaderiho
kostya.aderiho
@kaderiho
okey, thanks everyone
Gregg Roemhildt
@roemhildtg
Hi guys, did logging change in a recnet version of can-stache?
I'm seeing lots of new logs (in a production webpack build).
image.png
Sorry, that wasn't in a production build. Nevermind that message :0
Kevin Phillips
@phillipskevin
@Lighttree, about :point_up: October 31, 2018 5:34 AM
There is no difference between those get syntaxes
I always use get someProp() { ... } unless I need to pass arguments (for async getters)
then it has to be
someProp: {
  get(lastSet, resolve) {
    // ...
  }
}
the standard getter syntax (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/get) doesn't allow arguments