Naming Convention

[DhritiShikhar]

Expected behavior

There is a mix of naming convention in wit.

Example:
https://github.com/fabric8-services/fabric8-wit/blob/master/controller/test-files/iteration/show/ok.res.iteration.golden.json

active_status is snake case
startAt is camel case

Actual behavior

This is not harmful but we should really practice using one of the naming conventions for:
- better code readability
- consistency

[kwk]

To make things worse, we also have - in member names: created-at. For go code we should follow:

Finally, the convention in Go is to use MixedCaps or mixedCaps rather than underscores to write multiword names.

(source: https://golang.org/doc/effective_go.html#mixed-caps)

[kwk]

@DhritiShikhar you wrote: "There is a mix of naming convention in wit."

Do you mean in the response/request format or in the Go code.

[DhritiShikhar]

response/request format @kwk

[kwk]

See also https://github.com/golang/go/wiki/CodeReviewComments#mixed-caps