Skip to content

Avoid explicit requirement of .0 on whole numbers of seconds - #722

Merged
glenrobson merged 2 commits into
masterfrom
duration-number-wording
Oct 9, 2026
Merged

glenrobson merged 2 commits into
masterfrom
duration-number-wording

Conversation

@tomcrane

Copy link
Copy Markdown
Contributor

This is a partner to IIIF/api#2495

Addresses IIIF/api#2492

We don't need people to explicitly "type" their duration values to floating point numbers by adding a redundant .0 where th value happens to be a whole number. It's just a number.

@robcast robcast left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good. (I think the JSON spec not further distinguishing number is the strongest argument :-)

@glenrobson glenrobson added the meta: ready-to-merge Pull request is ready to merge into main branch label Oct 2, 2026
@glenrobson
glenrobson merged commit 870bcfb into master Oct 9, 2026
2 checks passed
@glenrobson
glenrobson deleted the duration-number-wording branch October 9, 2026 12:21

This branch was successfully deployed

1 active deployment
staging — 1c564d95 Deployed Oct 9, 2026 by github-actions[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

meta: ready-to-merge Pull request is ready to merge into main branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants