[OperationalInsights] Fix DateTimeOffset format string #34031
Merged
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.
Resolve #33536, #33571
The generated code should be
property.Value.GetDateTimeOffset("O")
instead ofproperty.Value.GetDateTimeOffset()
.The former method will call an extension method of
JsonElement
written by us to treat theJsonElement
as Int64 (Unix Timestamp) or string and the string case can support multiple formats despite the "O" format (ISO8601
) being passed in. See code.The latter method calls the original
GetDateTimeOffset()
ofJsonElement
and seems to only supportISO8601
format.Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.