format code about exported function should have comment

[chaosi-zju]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

format code about exported function should have comment

Which issue(s) this PR fixes:

Fixes part of #6078

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

[warjiang]

/assign

[chaosi-zju]

@RainbowMango

What do you think of the fix method in this PR?

here may still about 60+ place this kind lint error, shall I move forward to handle the rest?

[warjiang]

@RainbowMango

What do you think of the fix method in this PR?

here may still about 60+ place this kind lint error, shall I move forward to handle the rest?

@chaosi-zju the work is valuable for me. In this PR, exported rule under the revive linter indicate me that if I want to export something, I should make some comments, and that push me to think about the question, does it really need to export the struct or the function.

I think we should still move forward to fix kind of errors reported by revive.

[chaosi-zju]

I think we should still move forward to fix kind of errors reported by revive.

comments fixed, we can handle this PR first, I will submit another PR to handle the rest
a PR too large may complicates review

[warjiang]

I think we should still move forward to fix kind of errors reported by revive.

comments fixed, we can handle this PR first, I will submit another PR to handle the rest a PR too large may complicates review

+1

[warjiang]

/lgtm
/approve

[karmada-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: warjiang

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [warjiang]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment