Skip to content
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.

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

Some optional properties (of a Collection) are less optional than others #865

Open
algernon opened this issue Feb 2, 2024 · 0 comments
Open
Labels

Comments

@algernon
Copy link

algernon commented Feb 2, 2024

Some optional properties of a Collection, such as verification_link, description, and style_sheet seem to be included in the /api/collections/{alias} GET response, even if they're empty: they appear as "":

❯ curl -s "http://localhost:9080/api/collections/algernon" \
           -H "content-type: application/json" \
           -H "Authorization: Token ${TOKEN}" | jq .data.description
""

...while others, such as script, and signature do not appear in this, unless they're set. This makes it a tiny bit harder to implement serialization and deserialization for the Collection type, because I have to treat some of the optional properties more specially than the others.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants