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

Inconsistency in the way run statuses are displayed when deserialized vs printed #250

Open
KevinCLydon opened this issue Nov 2, 2022 · 0 comments
Labels
good first issue Good for newcomers

Comments

@KevinCLydon
Copy link
Member

The RunStatusEnum type gets converted to a string differently depending on whether it's deserialized using serde (which is what happens in the rest api) or using fmt::Display (which is used when printing or writing to the DB (I think?)). We should make them consistent (ideally always snake_case, probably). Ideally, we should see if there's a way to call into the serde code when using fmt::Display or vice versa.

@KevinCLydon KevinCLydon added the good first issue Good for newcomers label Nov 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant