Underscore separated field names vs Camel case

[jwrosewell]

Some classes and interfaces use underscore separated field names. For example the GetIdentityResponse class in the core.

Others use camel case. For example the Identity interface in the end points file.

Particularly where the data in the interface or class is the same it would be helpful to standardise on a naming convention.

My preference is camel case as it leads to shorter names but I don't have a strong view.

[OlivierChirouze]

Thanks James,

Actually we had the discussion regarding case on objects that are exported (cookies, messages). In this case and only in this case, we went for snake_case, even though there was not a strong driver.

This is why there are a couple of snake case attributes, they should all be in the generated model only.

All the rest must be using camel case as I believe this is more standard (but this is of course a matter of taste mostly).