microsoft / microsoft/AdaptiveCards
Update documentation to clarify what subset of RFC3339 we support for dates
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2k
- Forks
- 595
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 1
Description
Someone pointed out that we aren’t fully supporting RFC3339. Specifically, we don’t support fractional seconds and leap seconds (and possibly more, those were the examples they pointed out)
Fractional seconds
1985-04-12T23:20:50.52Z
Leap seconds
1990-12-31T23:59:60Z
This represents the leap second inserted at the end of 1990.
We should document this, and document what we actually support.
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
No file or test is named. Start by locating the date documentation and the code or tests that parse RFC3339 values, then compare supported behavior with the fractional-seconds and leap-second examples in the issue. Done means the documentation clearly states the supported RFC3339 subset and its limitations.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100