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

[confignet] Should we change the name of NetAddr and NetTCP to end in Config? #9509

Closed
mx-psi opened this issue Feb 7, 2024 · 3 comments · Fixed by #9614
Closed

[confignet] Should we change the name of NetAddr and NetTCP to end in Config? #9509

mx-psi opened this issue Feb 7, 2024 · 3 comments · Fixed by #9614
Labels
area:config release:required-for-ga Must be resolved before GA release

Comments

@mx-psi
Copy link
Member

mx-psi commented Feb 7, 2024

          Few others:
  • NetAddr -> AddrConfig?
  • NetTCP -> TCPConfig?

Originally posted by @bogdandrutu in #9474 (comment)

@bogdandrutu
Copy link
Member

Also we duplicate the "net" prefix in config[net].[Net]Addr for example

@arjunmahishi
Copy link
Contributor

arjunmahishi commented Feb 10, 2024

Taking this up.


NetTCP -> TCPConfig?

@bogdandrutu I am assuming, by this you mean TCPAddr ?

// TCPAddr represents a TCP endpoint address.
type TCPAddr struct {


EDIT: Nevermind. I missed the PR that already addresses this.

arjunmahishi added a commit to arjunmahishi/opentelemetry-collector that referenced this issue Feb 10, 2024
This commit renames the following structs:

* NetAddr to AddrConfig
* TCPAddr to TCPConfig

Fixes open-telemetry#9509
bogdandrutu pushed a commit that referenced this issue Feb 13, 2024
**Description:** 

Rename types in `confignet` to adapt to conventions (avoid stuttering
and end in `Config`)

**Link to tracking Issue:** Updates #9509
@TylerHelmuth
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:config release:required-for-ga Must be resolved before GA release
Projects
Archived in project
4 participants