Skip to content

Align S-038 wording with the OpenAPI Format Registry framing#370

Merged
hdamker merged 1 commit into
camaraproject:mainfrom
hdamker:chore/s038-registry-wording
Jul 8, 2026
Merged

Align S-038 wording with the OpenAPI Format Registry framing#370
hdamker merged 1 commit into
camaraproject:mainfrom
hdamker:chore/s038-registry-wording

Conversation

@hdamker

@hdamker hdamker commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

What type of PR is this?

  • cleanup

What this PR does / why we need it:

Aligns the S-038 (camara-integer-safe-range) wording with the rationale agreed in camaraproject/Commonalities#648: the Design Guide §2.2 constraint is expressed via the OpenAPI Format Registry recommendation for int64 — the 53-bit integer range and double-precision (binary64) JSON parsing — rather than JavaScript specifics (camaraproject/Commonalities#667).

Reworded: rule description in .spectral-r4.yaml, the finding message and header comment in camara-integer-safe-range.js, and the test class docstring. The range threshold and rule behavior are unchanged.

Which issue(s) this PR fixes:

No tooling issue — wording follow-up to camaraproject/Commonalities#648 / camaraproject/Commonalities#667.

Special notes for reviewers:

No functional change; tests assert rule code and finding paths, not message text. TestS038IntegerSafeRange and test_rule_metadata_integrity.py pass.

Changelog input

 release-note
Aligned S-038 (camara-integer-safe-range) wording with the OpenAPI Format Registry int64 recommendation (53-bit integer range); no behavior change.

Additional documentation

This section can be blank.

docs

@rartych rartych 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.

LGTM

@hdamker hdamker merged commit 660a75d into camaraproject:main Jul 8, 2026
8 checks passed
@hdamker hdamker deleted the chore/s038-registry-wording branch July 8, 2026 12:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants