Skip to content

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

@hballangan-mdsol

Description

@hballangan-mdsol

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!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions