Where have you seen that? I always see camelCase: as api payloads on the web, in tools (tsconfig, package.json, VS Code's config).
A weird exception would be AWS CloudFormation configs (PascalCase), but that's because they're copying Java SDK conventions.
Building Murmur. Previously Software Engineer at @Webflow. I write about building software, CI/CD, Distributed Teams, personal growth, & individual productivity.
RESTful API guidelines historically have encouraged snake case. camel case has started to be more prolific so it's an equally good option but I've been on a support call at least twice where someone had improper case for a JSON field and it led to debugging an issue that would not have been an issue with snake case.
I should also mention that snake case has been the case type for many ruby, perl and python based RESTful APIs and the things you've listed are JS based and tools.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm unfamilliar with
Where have you seen that? I always see camelCase: as api payloads on the web, in tools (tsconfig, package.json, VS Code's config).
A weird exception would be AWS CloudFormation configs (PascalCase), but that's because they're copying Java SDK conventions.
RESTful API guidelines historically have encouraged snake case. camel case has started to be more prolific so it's an equally good option but I've been on a support call at least twice where someone had improper case for a JSON field and it led to debugging an issue that would not have been an issue with snake case.
I should also mention that snake case has been the case type for many ruby, perl and python based RESTful APIs and the things you've listed are JS based and tools.