Add AccurateDuration and NominalDuration Scalars #132
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds support for two scalars:
AccurateDuration
(which maps to ajava.time.Duration
).NominalDuration
(which maps to ajava.time.Period
).Both of these heavily relate to durations as defined in ISO 8601 but with the following caveats:
AccurateDuration
only relates to the portion of a duration that is context-free (i.e. does not need to know the calendar position to determine its value). It maps to ajava.time.Duration
.NominalDuration
relates to the portion of a duration that is dependent on knowing the calendar position to determine its value. It maps to ajava.time.Period
.The naming of these are strongly influenced by the wording in ISO 8601:
The code here follows the same pattern as that used for the
DateTime
Scalar.Please see graphql/graphql-scalars#24 for the specification of
AccurateDuration
andNominalDuration
.