Currently the output of /api/v1/info endpoint returns a JSON string that the keys are sometimes in camelCase and sometimes they are in kebab-case. Which is really annoying to work with from the frontend or tests. The main reason behind this is that we use kebab-case inside TOML files for writing relayer configuration, but camelCase when we export this information to the outside world. it is by convention that TOML files uses kebab-case and JSON is camelCase.
Task Checklist
[ ] Make sure that all fields are in camelCase when exported.
shekohex
commented
1 year ago
Overview
Currently the output of
/api/v1/infoendpoint returns a JSON string that the keys are sometimes in camelCase and sometimes they are in kebab-case. Which is really annoying to work with from the frontend or tests. The main reason behind this is that we use kebab-case inside TOML files for writing relayer configuration, but camelCase when we export this information to the outside world. it is by convention that TOML files uses kebab-case and JSON is camelCase.Task Checklist