Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

logging: Change logNumericsAsNumbers to numerics and add docs #6002

Merged
merged 1 commit into from
Nov 9, 2019

Conversation

theopolis
Copy link
Member

This is an API change for the format of logged events. The top-level log field "logNumericsAsNumbers" was introduced to help migrate from string-encoded numerics to JSON numbers.

This change updates the field to be "numerics", updates the flag to conform to flag naming conventions, and documents the expectation.

This is an API change for the format of logged events.
The top-level log field "logNumericsAsNumbers" was introduced to help
migrate from string-encoded numerics to JSON numbers.

This change updates the field to be "numerics", updates the flag to
conform to flag naming conventions, and documents the expectation.
Copy link
Member

@directionless directionless left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This feels reasonable safe to me -- It's adding a field, which can be ignored by consumers. But it's not changing the meanings of the others.

@theopolis
Copy link
Member Author

Yeah, also the field is already included (using a different name) for the 4.0.2 release. That's not great but ideally we'd talk longer about adding new fields, what they should be called, if they are needed, etc. This is a good feature to have, hopefully we can switch the default to not be 'all strings all the time' in the future. This will require some comms / planning.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants