Standardisation of Twilio Segment user traits

Segment internally treats camelCase and snake_case the same and explicitly encourages interchangeable use in their documentation. When user properties get pushed into the Vero destination from Segment, these are treated as different traits, e.g. first_name and firstName. The expected behaviour would be to standardise user traits and event properties coming from Segment to the Vero default (snake case) like other destinations do this. As this may be a breaking change for some users, a lab switch to 'standardise or not standardise' would be a great too. That said: https://xkcd.com/1172/ Ref: https://segment.com/docs/connections/spec/identify/#traits Note: If this integration is maintained by Segment and not Vero let me know and I'll raise a ticket with their team directly.