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

Enable unexported-return linter rule #18370

Open
6 tasks
ivanvc opened this issue Jul 26, 2024 · 7 comments
Open
6 tasks

Enable unexported-return linter rule #18370

ivanvc opened this issue Jul 26, 2024 · 7 comments
Assignees
Labels
area/testing priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. type/cleanup

Comments

@ivanvc
Copy link
Member

ivanvc commented Jul 26, 2024

What would you like to be added?

There are two remaining linter rules that we haven't enabled but are left as TODO (./tools/.golangci.yaml): exported and unexported-return. The former will have significant changes to exported functions and interfaces. The latter, even though it impacts exported structs, it's for the better (it exposes them without breaking client implementations).

I suggest breaking the pull requests into small tasks like we did on #17578.

The following modules have warnings to be addressed:

  • api
  • pkg
  • client/pkg
  • client/v3
  • server
  • tests

Refer to the attached log file with the result from KEEP_GOING_MODULE=true make verify-lint.

Why is this needed?

To improve the quality of the code.

@ivanvc ivanvc added area/testing type/cleanup priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Jul 26, 2024
@ivanvc
Copy link
Member Author

ivanvc commented Jul 26, 2024

/assign @thedtripp

@k8s-ci-robot
Copy link

@ivanvc: GitHub didn't allow me to assign the following users: thedtripp.

Note that only etcd-io members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @thedtripp

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@ivanvc
Copy link
Member Author

ivanvc commented Jul 26, 2024

@jmhbnz, could this be a bug? @thedtripp is already part of our org 🤔

Edit: I think it's because he doesn't belong to any teams. Should he open a pull request to add himself to the members? (https://github.com/kubernetes/org/blob/main/config/etcd-io/sig-etcd/teams.yaml#L77)

@thedtripp
Copy link
Member

I'd like to work on this issue.

@thedtripp
Copy link
Member

/assign @thedtripp

@jmhbnz
Copy link
Member

jmhbnz commented Jul 28, 2024

@jmhbnz, could this be a bug? @thedtripp is already part of our org 🤔

Edit: I think it's because he doesn't belong to any teams. Should he open a pull request to add himself to the members? (https://github.com/kubernetes/org/blob/main/config/etcd-io/sig-etcd/teams.yaml#L77)

Good spotting - Yes this should be tidied up, @thedtripp please feel free to raise a kubernetes/org pr to add yourself to the members team 🙏🏻

@thedtripp
Copy link
Member

@jmhbnz, could this be a bug? @thedtripp is already part of our org 🤔
Edit: I think it's because he doesn't belong to any teams. Should he open a pull request to add himself to the members? (https://github.com/kubernetes/org/blob/main/config/etcd-io/sig-etcd/teams.yaml#L77)

Good spotting - Yes this should be tidied up, @thedtripp please feel free to raise a kubernetes/org pr to add yourself to the members team 🙏🏻

I'll raise that PR in the next few days. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/testing priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. type/cleanup
Development

No branches or pull requests

4 participants