Tools Module - Re: 3.2.4 messagetime
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 53
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Currently this states:
Supported values: 24 hour date time format. DD.MM.YEAR.HOUR.MM - DD.MM.YEAR.HOUR.MM where the second date is an optional exclusive expiry date.
May I suggest that this pattern is actually something of an anti-pattern (or at least, is "non-standard"). Can I propose that instead we require the date format to follow the ISO 8601 (Date and Time Standard) which takes the format:
2018-09-17T16:48:58Z
(YYYY-MM-DDTHH:MM:SS + Z which denotes UTC)
Additionally, the ISO notation allows the author to specify the time based on either UTC or with a UTC off-set (which is not addressed in the current draft)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing section 3.2.4, including its current message-time format. Compare the proposed ISO 8601 representation with the existing requirement and determine how UTC offsets should be handled; done means the specification records a decided format and expiry-date behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100