Skip to content

Allow versioning the scalar urls #34

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

Closed
martinbonnin wants to merge 2 commits into from
Closed

Allow versioning the scalar urls #34

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7a436a9
Update Custom Scalar version naming guidelines
martinbonnin Nov 28, 2025
57d1db8
format
martinbonnin Nov 28, 2025
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
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,9 +55,9 @@ Specification semantics must not change, as specifications are publicly
available reference documents. We will permit small edits which do not change
specification semantics, such as typo fixes.

A new version of a Custom Scalar specification should have a new scalar name,
either with a number appended such as `<scalar-name>2`, or a different name such
as `OffsetDateTime` to differentiate from `DateTime`.
A new version of a Custom Scalar specification can either use a new scalar name
or add a version as part of its url like
`scalars/contributed/<github-user-name>/<version>/<scalar-name>.md`.

## Licensing

Expand Down