Inconsistent naming in device registration API JSON (case style)
See original GitHub issueIn the Device Registry Management API, the fields in the Device
JSON structure related to the gateway groups feature are defined in camel-case notation:
"viaGroups": [
"string"
],
"memberOf": [
"string"
],
However, in the other parts of the API, the kebab-case notation is used (e.g. auth-id
, minimum-message-size
, resource-limits
, etc.).
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:11 (7 by maintainers)
Top Results From Across the Web
Fields name policy converters · Issue #33 · Kotlin/kotlinx ...
A very common case of serialization is when API/JSON naming policy ... violates Kotlin code style guides and backward incompatible.
Read more >JSON Naming Convention (snake_case, camelCase or ...
My team consistently follows this convention when building REST APIs. There are some reasons: First, the JSON convention should be independent ...
Read more >Encoding/Decoding JSON with camelCase keys - Eneko Alonso
This convention uses lower camel case ( camelCase ) for object/struct property names. In this scenario, we can encode/decode JSON objects ...
Read more >Naming conventions - Hackolade
A case conversion may be applied in the conversion parameters, cfr below. Example: Business Name,Technical Name,Optional Description. account,acct,. customer, ...
Read more >Zalando RESTful API and Event Guidelines
API design principles. Comparing SOA web service interfacing style of SOAP vs. REST, the former tend to be centered around operations that are...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
So my 👍 was for fixing the inconsistency by using “kebab-case”.
Ok, then I will unschedule this issue from 2.0.0