You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/partners/sources.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ Within the Spec, there are a few requirements for partner Streams worth pointing
38
38
39
39
### Naming Conventions
40
40
41
-
When you're creating events and the properties associated with them, you want to be crystal clear about the casing. This might seem nitpicky, but it's imperative in the long run. We recommend `Proper Case` for event names, and `snake_case` for properties. If you need to deviate for specific reasons to your platform this is allowable.
41
+
When you're creating events and the properties associated with them, you want to be crystal clear about the casing. This might seem nitpicky, but it's imperative in the long run. We recommend `Proper Case` for event names, and `snake_case` for properties. If you have platform-specific requirements that necessitate the use of different casing, it is permissible.
0 commit comments