canjs/canjs

We CAN build the impossible! https://codepen.io/justinbmeyer/pen/yEGGoK

Gregg Roemhildt

@roemhildtg

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

@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

Matthew Phillips

@matthewp

https://forums.donejs.com/t/bulk-actions-destroy-update-on-multiple-items/575

I think that's the forum post @justinbmeyer is talking about

the linked to jsbin shows an example that does bulk deletes

Frank Lemanschik

@frank-dspeed

ya the question now is do you want to do bulk on the interface aka from the client side

or from the backend aka batch bulk enabled api endpoint

Justin Meyer

@justinbmeyer

@jeroencornelissen I think I shared some code too

Frank Lemanschik

@frank-dspeed

https://jsbin.com/noguwup/9/edit?html,js,output

this is your code

it adds a destroyList method

that sends the json to a endpoint that does the foreach

Where communities thrive

People

Repo info

Activity