JsonRest store auto save? about dgrid HOT 7 CLOSED

If you want to avoid the GET request there are a couple options. You could set the grid.getBeforePut property to false. Or you could use the dojo/store/Cache wrapper with the JsonRest store to use a store level cache. If you are looking to get a PUT request rather than a POST request, you probably need to set the idProperty on the JsonRest store to a valid unique property on the objects. Does this help?

from dgrid.

Hello, thank you for the replies. Its not so much the number or type of requests that i'm concerned about, its more the fact that the request to store the document ( the POST / PUT ) seems to have exactly the same content as the original rather than to contain the updated information taken from the grid.

I'm not really sure that the comments above have resolved this. Thanks.

from dgrid.

I see, sorry for the misunderstanding. However, I am not able to reproduce this problem. When I setup an Editor with a checkbox and autoSave, the data that is sent to the server has a property value of true when the checkbox is checked and false otherwise. Do you think you could include a test case for this issue?

from dgrid.

Thank you for re-opening and no problem about the confusion. My code is quite embeded in my application and so might be difficult to pull out. I will see what i can do though. However, it sounds like you have a simple test case... does that use a JsonRest Store also? If so, would you mind making that available to me so that i could test it and perhaps see what the differences are with my code? Thanks.

from dgrid.

Yes, here is the latest test case for using the JsonRest store:
https://github.com/kriszyp/dgrid/blob/rest/test/JsonRest.html
It includes a column with autoSave on.

from dgrid.

For what it's worth, that updated test should be available in the master branch of the SitePen repository now as well.

Is this still an issue for you? Can you manage to reproduce it using the simple JsonRest test in the dgrid repository as a base?

from dgrid.

Closing this since we haven't heard back in a while. Feel free to open a new issue if you have further reproducible problems.

from dgrid.