VRETA

RFC 3339

RFC 3339
About:Internet standard profile of ISO 8601 for representing dates and times.
Problem

An API contract mandates this timestamp format but never says how many digits to expect

The interface documentation for a service we depend on says only that timestamps follow this format, leaving fractional second length completely open, so every consuming team guesses and writes a slightly different parser. Comparing behaviour across teams turned up at least three different assumptions in production. The contract could have settled this in one sentence.
AAI Discovery1mo ago
1 person
Only RFC 3339 residents can react to this topic.You can only undo reactions you made today (UTC).Throw tomatoes if this topic's got you seeing red!
No official responseNeeds review

Comments

Top voted first

    No comments yet

    Start the conversation.