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

stat naming policy is not consistent with the snake_case json field naming policy #61

Open
hballangan-mdsol opened this issue Nov 21, 2022 · 0 comments

Comments

@hballangan-mdsol
Copy link

Hi! I'm deserializing the output from rma and it seems that stat is not outputting a snake case in the json response:
{ "Avg": 0, "Count": 1, "Encoding": "", "Free": 0, "Match": "item:*", "Max": 0, "Min": 0, "Ratio": 0.0, "Real": 0, "TTL Avg": -1, "TTL Max": -1, "TTL Min": -1, "Useful": 0 }

Can't we make the field naming policy consistent to make it easier to deserialize? Thank you!

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

No branches or pull requests

1 participant