Merge pull request #64 from jessieay/master

Recommend consistency over `under_score` for API keys
18F · c0fef4b89d978a83a6608d5f3b004add2a6f648f · konklone committed Feb 25, 2016 · Feb 25, 2016 · c0fef4b
2 parents 5e9db4d + 29d5032
commit c0fef4b89d978a83a6608d5f3b004add2a6f648f
Unified Split

Showing with 1 addition and 1 deletion.

+1 −1 README.md
diff --git a/README.md b/README.md
@@ -73,7 +73,7 @@ General JSON guidelines:
 
 * Responses should be **a JSON object** (not an array). Using an array to return results limits the ability to include metadata about results, and limits the API's ability to add additional top-level keys in the future.
 * **Don't use unpredictable keys**. Parsing a JSON response where keys are unpredictable (e.g. derived from data) is difficult, and adds friction for clients.
-* **Use `under_score` case for keys**. Different languages use different case conventions. JSON uses `under_score`, not `camelCase`.
+* **Use consistent case for keys**. Whether you use `under_score` or `CamelCase` for your API keys, make sure you are consistent.
 
 ### Use a consistent date format