Skip to content
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

Add guidance on when to use and not use nested namespaces #1197

Conversation

tigrannajaryan
Copy link
Member

This topic has come up at least 3 times now. I believe a clarification is
warranted. The clarification is aligned with previous recommendations:
#789 (comment)
#882 (comment)
#1194 (comment)

This topic has come up at least 3 times now. I believe a clarification is
warranted. The clarification is aligned with previous recommendations:
open-telemetry#789 (comment)
open-telemetry#882 (comment)
open-telemetry#1194 (comment)
Copy link
Member

@Oberon00 Oberon00 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it make sense to specifically call out the process namespace here, which seems to be rather popular?

@tigrannajaryan
Copy link
Member Author

Would it make sense to specifically call out the process namespace here, which seems to be rather popular?

I am not sure how exactly to do it nicely. Can be improved in a future PR by someone else.

@bogdandrutu bogdandrutu merged commit 4052a2c into open-telemetry:master Nov 10, 2020
@tigrannajaryan tigrannajaryan deleted the feature/tigran/namespace-nesting branch March 3, 2022 17:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants