Nicolas Perriault

> especially because that's not defining an input. JSON Schema doesn't define inputs but data structures, and a string is a perfectly valid one. So we need to find a...

refs https://github.com/mozilla-services/react-jsonschema-form/issues/159

Without any specific syntax to do that in one request on the server endpoint, yes, exactly. Note that these two calls could be perform in a single batch operation anyway.

Ah, true. No big deal anyway.

After a quick discussion with @ametaireau, here's the current state of our thinking on this: - Having transactions would provide a neat way to cancel local persistence operations; - It...

#303 has now landed and is a huge step towards this goal.

> We should provide a share this record and share this collection feature. I think. Indeed. Something like this would be convenient: ``` js const db = new Kinto(); const...

I'd rather use `share/unshare` here, as a synced collection is already _published_ for the user.

We should probably expose the permissions in the record objects, but that would mean synchronizing them as well...

That means not rejecting when encountering a conflict but getting the resource and resolving with the result instead, right?