Releases: earthstar-project/earthstar-graphql
Releases · earthstar-project/earthstar-graphql
v6.1.1
v6.1.0
v6.0.0
6.0.0
Breaking
syncWithPub
(which synced a workspace with a single pub), andsyncMany
(which synced many workspaces with many pubs) have been removed in favour of a singlesyncWithPubs
mutation which syncs a single workspace with many pubs. I think this is the sweet spot.
Features
- Added a
removeWorkspace
mutation which removes a workspace with a given address from the context. It can be authorised using acanRemoveWorkspace
checking function provided to the schema. - When a workspace with an invalid address is created during the
addWorkspace
,syncWithPub
, orsyncMany
mutations, the error will be gracefully caught and made part of the expected GraphQL response.
Fixes
- Fixes an issue where no value could be passed to a non-nullable filed when syncing.
- Fixes bad values being passed to the pulled documents in a DetailedSyncSuccess
v5.1.1
v5.1.0
v5.0.0
5.0.0
Breaking
- The
format
arg on thesyncWithPub
mutation has been removed, as whether a pub is a GraphQL or REST pub is now automatically determined.
Features
- Added a
isGraphQlPub
function export which can be used to determine whether the pub at a URL is a GraphQL pub or not. - Added a optional
deletedAfter
arg to theset
mutation so that ephemeral documents can be created - If the workspace passed to a
syncWithPub
mutation does not exist,syncWithPub
will create it if it passes the configurablecanAddWorkspace
check.
Internal
- earthstar dependency updated to 5.2.3
- earthstar moved into peer dependencies, as clients which may also depend on the earthstar package should use the same version.
v4.2.0
4.2.0
Improvements
- Added a
displayName
field to theAuthor
type, which returns the display name set by the author at a particular path in a workspace (see https://github.com/earthstar-project/earthstar/blob/master/docs/vocabulary.md#author)
v4.1.1
v4.1.0
v4.0.1
4.0.1
Fixes
- Fixed an issue where a schema context configured with no sync filters would wrongly respond to queries for its sync filters as empty arrays.
- I think these two should be semantically different: an undefined sync filter means the pub has no preference on documents, whereas an empty one would mean the pub is accepting nothing. (???)