Where communities thrive


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

    greenkeeper[bot] on @octokit

    (compare)

  • 03:57

    greenkeeper[bot] on @octokit

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

  • 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
Kevin Phillips
@phillipskevin
obviously, not a great workaround :smile:
Gregg Roemhildt
@roemhildtg
That's what I'm doing for now. It works fine, but yeah eventually a nice polished devtools will be good, which I'm sure you'll get to. I mean its already so much easier to debug than a year ago, and having the viewmodel editor makes it a lot easier to get others up to speed on the stuff I'm working on
Good documentation is one thing...but being able to play with the viewmodel in dev tools makes it super simple
Kevin Phillips
@phillipskevin
:thumbsup: we'll keep improving it
Gregg Roemhildt
@roemhildtg
I'm thinking I might even build the viewmodel editor into demo projects.
Kevin Phillips
@phillipskevin
yeah, I'm going to post on the forums how to add it to demo pages
Gregg Roemhildt
@roemhildtg
Not sure how feasible that is at the moment but having a sort of editor like some libs have would be a really nice tool
Kevin Phillips
@phillipskevin
it's not too bad to add to demo pages
Gregg Roemhildt
@roemhildtg
Okay :)
I wonder, like down the road could the view model editor get passed a tag, like componentSelector:raw="my-component"
And then the viewmodel editor would just pick that component's viewmodel?
That would make it super easy to embed in a demo
Kevin Phillips
@phillipskevin
yeah, that would be tough
well, we could create a component that wraps the current one and does that
but for it to work in devtools it can only take in serialized data
Kevin Phillips
@phillipskevin
same-comp-fix.gif
@roemhildtg here's the fix for that issue... I'm going to put the index of that element in the tagName
and reset the data when the tagName changes
Viktor Busko
@Lighttree
Guys is there big difference between such getters in VM ?
get someProp() {
        return 'something';
},

// VS

someProp: {
    get() {
         return 'something';
    }
}
Maybe some preferences when to use
kostya.aderiho
@kaderiho

Hi guys, is there any way to save DefineList data on the server using PUT request?

For instance:

const Todo = DefineMap.extend({ ... some properties ... });

Todo.List = DefineList.extend({ "#": Todo });

let TodosList = new Todo.List([ ...several items there... ]);

// send PUT request here with TodoList inside of the body

Thank you in advance

Matthew Phillips
@matthewp
are you using can-rest-model?
kostya.aderiho
@kaderiho
So I'm using canjs v3 and can-connect as a middleware for data layer
Matthew Phillips
@matthewp
ok cool
so when you call .save() what happens?
Oh, do you mean you need it to use PUT even for new items?
kostya.aderiho
@kaderiho
I need to use PUT for already retrieved items by .getList method. If I understand correctly I can not do TodoList.save() because .save works for one instance only
Matthew Phillips
@matthewp
why can't you do todoList.forEach(todo => todo.save()) ?
kostya.aderiho
@kaderiho
It's an option but it will cause a lot of requests in case of large list :)
Matthew Phillips
@matthewp
There's the combine-requests behavior that combines requests together
not sure if it works for saving though...
pinging @justinbmeyer in case he has a solution for this
I think combine-requests only works for getting lists
Justin Meyer
@justinbmeyer
I think someone asked this and posted solution in the forums
kostya.aderiho
@kaderiho
Seems that combineRequests works only for get (getListData) requests (according to the documentation), is it correct guys or not?
Frank Lemanschik
@frank-dspeed
i would say
1 reqest per save is total ok
if you need to save more data then simply do a custom batch via a endpoint that supports that
Matthew Phillips
@matthewp
@kaderiho yep, that is correct
Frank Lemanschik
@frank-dspeed
but out of my view you should save the item on creation
there is no case where you save more then 1 item at time and if you batch edit items via your interface directly
you end up in 1 request per processed item
thats total ok
else simply send item ids and changes to the backend and process them there
a batch endpoint would be a simple endpoint that accepts json lists
then you do getList and post that json to that endpoint
your done
the endpoint then takes that json list and does the for each serverside