Text description aligment for duration format fields #459
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
PedroDiez
requested review from
jlurien,
patrice-conil,
rartych and
shilpa-padgaonkar
as code owners
rartych
reviewed
May 12, 2025
Co-authored-by: Rafal Artych <121048129+rartych@users.noreply.github.com>
rartych
reviewed
May 14, 2025
Co-authored-by: Rafal Artych <121048129+rartych@users.noreply.github.com>
rartych
previously approved these changes
May 20, 2025
Kevsy
reviewed
May 21, 2025
Kevsy
reviewed
May 21, 2025
Collaborator
|
Very minor typo correction above otherwise LGTM |
Co-authored-by: Kevin Smith <Kevsy@users.noreply.github.com>
Co-authored-by: Kevin Smith <Kevsy@users.noreply.github.com>
rartych
approved these changes
Jun 2, 2025
patrice-conil
approved these changes
Jun 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
What type of PR is this?
What this PR does / why we need it:
Provide an aligned text description for duration format fields as explained in #458.
In this way, it avoids additional WG discusions on which description text use.
Which issue(s) this PR fixes:
Fixes #458
Does this PR introduce a breaking change?
Special notes for reviewers:
Suggested Note added just to inform Subproject about ambigüity that may generate use of duration fields.
Also use of a start date/time field in combination with a
durationformat field could help to mitigate ambiguity topics (added also to inform Subproject, at the end it will be up to their consideration) .Info about this:
Changelog input
Additional documentation
This section can be blank.