Skip to content

v0.1.3: BREAKING: hasImages → hasCC0Image rename; all_not_found error

Choose a tag to compare

View all tags
@cyanheads cyanheads released this 04 Jun 09:38
v0.1.3
This tag was signed with the committer’s verified signature.
cyanheads Casey Hand
SSH Key Fingerprint: lkZCAfVCK5qsrcvEYCs0BnVRDCX7pKsdCZkw5yYKMuw
Verified
Learn about vigilant mode.
fc353b4
This commit was signed with the committer’s verified signature.
cyanheads Casey Hand
SSH Key Fingerprint: lkZCAfVCK5qsrcvEYCs0BnVRDCX7pKsdCZkw5yYKMuw
Verified
Learn about vigilant mode.

BREAKING: hasImages → hasCC0Image rename; all_not_found error

BREAKING: met_get_object renames the hasImages output field to hasCC0Image. Consumers reading result.objects[].hasImages must update to result.objects[].hasCC0Image. Value semantics are unchanged — true when a CC0 open-access image URL is available.

Changed:

  • hasImages → hasCC0Image on met_get_object output (#1) — clarifies the field signals a CC0 image, distinct from met_search's hasImages filter (which matches copyrighted works too)

Added:

  • all_not_found error on met_get_object (#2) — fires when every objectID returns HTTP 404, with recovery hint to verify IDs via met_search; previously all-failure paths threw all_failed regardless of cause
  • kind discriminator on internal FailItem type for 404-vs-network classification

16 tests pass; bun run devcheck clean.

Assets 3
Loading