Exported names

[johnabass]

candlelight primarily concerns itself with tracing. Therefore, putting trace in exported names is redundant. ConfigureTracerProvider and TraceMiddleware would be better as ConfigureProvider and Middleware respectively.

The motivation is how this code looks from a client perspective. Recall that in golang, one cannot elide the package name. A client sees candlelight.ConfigureTracerProvider and candlelight.TraceMiddleware. Both are overly verbose if the candlelight package doesn't create any other kinds of provider or middleware.

Additionally, if ConfigureProvider is playing the role of a constructor, then NewProvider would be a better name.

Excellent guidance on naming is in Effective Go:

https://golang.org/doc/effective_go#names

[Sachin4403]

Hi @johnabass

In the future when we will have support for metrics and other things then this function name ConfigureTraceProvider, TraceMiddleware will help us to easily identify what this function is doing.