Currently adding a workspace to a context can only be done by triggering the sync mutation with an unseen workspace address. This isn't very clear.
Instead, I'd like to add an explicit addWorkspace mutation, which takes an address and optionally an AuthorInput as its arguments (explained below)
As earthstar-graphql can be run within trusted and untrusted environments (ie. in a client or deployed online), the check for whether a workspace can be added needs to be completely configurable.
I am thinking this would be a checking function that you can pass to context, which you could configure with your own block or allowlist, or identities allowed to add workspaces (hence the optional authorinput that can be sent with the mutation).
Currently adding a workspace to a context can only be done by triggering the
syncmutation with an unseen workspace address. This isn't very clear.Instead, I'd like to add an explicit
addWorkspacemutation, which takes an address and optionally an AuthorInput as its arguments (explained below)As earthstar-graphql can be run within trusted and untrusted environments (ie. in a client or deployed online), the check for whether a workspace can be added needs to be completely configurable.
I am thinking this would be a checking function that you can pass to context, which you could configure with your own block or allowlist, or identities allowed to add workspaces (hence the optional authorinput that can be sent with the mutation).