Repository navigation
Use camelCase keys in health schema v4 - #27
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Health v3 mixes uppercase and snake_case keys. This change emits v4 with c, fm, uptimeS, txStarted, txDone, txFailed, txTimeouts and queueDrops; v, boot and neighbors retain their names. Values, string types, cadence and local routingDiagnostics v2 remain unchanged.
Validation: actual-source host regression passed 1,522 checks with address/undefined-behaviour sanitizers; maximum actual-counter payload was 207/228 bytes. Routing regression and local DMS formatter preservation checks passed.
Not flashed or deployed. Consumers must retain historical v3 support and accept v4 before rollout; Phoenix dependency pins are unchanged.