-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Module and directory naming convention #2
Comments
I'm going to follow the convention of |
I did Whether this is Hell, for elixir integrations we could have a single app and do I guess also |
Yeah, I get a little uncomfortable with the last word in a module matching the last word in another module eg. Strikes me you could have a At the top level, you could have one app try to drag them all in, but eventually you'd run into trouble when integrations for modules X and Y turned out to have different requirements for a shared dependency Z. |
Oh, bit of a corner: if I'm not creating a directory under |
Opentelemetry
orOpenTelemetry
?OpenTelemetrySomething
orOpenTelemetry.Something
? I was initially surprised at the former but I like how it avoidsalias
clashing with theSomething
opentelemetry/something
oropen_telemetry/something
oropen_telemetry_something
oropentelemetry_something
?Asking because I've already been inconsistent in my
opentelemetry_honeycomb
and this project is doing something else again. :)The text was updated successfully, but these errors were encountered: