You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have "read hooks" which are meant for retrieving data via the core api. Now we need "write hooks" in order to create and update data via the core api.
Non-exhaustive list of functionality that's needed:
set device info
accept an invite
reject an invite
request invite cancellation
send an invite
add a server peer
create a blob (might not actually expose this one since this would mostly be used internally by something like creating/updating a document)
set device as archive device
create a document
update a document
delete a document
create a project
leave a project
update project settings
import a project configuration
Another notable thing that was discussed is to to have the document create+update handle creating blobs + attachments internally i.e. something like:
We have "read hooks" which are meant for retrieving data via the core api. Now we need "write hooks" in order to create and update data via the core api.
Non-exhaustive list of functionality that's needed:
Another notable thing that was discussed is to to have the document create+update handle creating blobs + attachments internally i.e. something like:
If we want to "remove" attachments with this approach, the intention is to omit the attachment references in the
value
that's specified above.For a potential return value for most of the hooks, we discussed something along the lines of:
Most of the above would be derived from what React Query provides, although I can some changes:
mutate
field (more cosmetic than anything else)Questions:
WriteHookResult
look sufficient for our needs?The text was updated successfully, but these errors were encountered: