Skip to content

Clarify key usage when releasing attributes #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
drazzilb91 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Clarify key usage when releasing attributes #5

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/guide/write_client.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -287,7 +287,7 @@ On the other hand, let's imagine we're writing a client for updating manually en

### Releasing attributes

If we don't want to own an attribute any more, we can release it too. This will give up ownership to another service the user has connected that can fill it, or otherwise disable the attribute. The release call looks just like acquiring, except we send our array of JSON objects to `https://exist.io/api/2/attributes/release/`.
If we don't want to own an attribute any more, we can release it too. This will give up ownership to another service the user has connected that can fill it, or otherwise disable the attribute. The release call looks just like acquiring, except we use the `name` key (even if we used `template` to acquire the attribute) and we send our array of JSON objects to `https://exist.io/api/2/attributes/release/`.

## Creating a new attribute

Expand Down