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.

Sign up for GitHub

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

Jump to bottom

Should eventhubs be in sdk/messaging or sdk/eventhubs ? #6411

Closed
antkmsft opened this issue Feb 12, 2025 · 2 comments
Closed

Should eventhubs be in sdk/messaging or sdk/eventhubs ? #6411

antkmsft opened this issue Feb 12, 2025 · 2 comments
Assignees
@LarryOsterman
Labels
Client This issue points to a problem in the data-plane of the library. Event Hubs needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team

Comments

@antkmsft
Copy link
Member

antkmsft commented Feb 12, 2025 •
edited
Loading

In Go, eventhubs are located in sdk/messaging.

In Rust and C++, they are in sdk/eventhubs.

I am going to open an issue for all 3 repos, if we want some consistency.

See also #6412 (same question about security/keyvault)
@github-actions github-actions bot added Client This issue points to a problem in the data-plane of the library. Event Hubs needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team labels Feb 12, 2025
@github-actions GitHub Actions
Copy link

Thank you for your feedback. Tagging and routing to the team member best able to assist.

This was referenced Feb 12, 2025
Closed
Closed
Open
@LarryOsterman
Copy link
Member

Go is the exception to the convention applied to all SDKs, we should not follow the Go naming rules.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@LarryOsterman LarryOsterman

Labels
Client This issue points to a problem in the data-plane of the library. Event Hubs needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@LarryOsterman @antkmsft