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

Fix linting error #70

Closed
tboerger opened this issue Nov 4, 2016 · 12 comments
Closed

Fix linting error #70

tboerger opened this issue Nov 4, 2016 · 12 comments
Labels
type/enhancement An improvement of existing functionality
Milestone

Comments

@tboerger
Copy link
Member

tboerger commented Nov 4, 2016

Currently the go linter errors out on various places, we should fix that to increase the code quality.

@tboerger tboerger added the type/enhancement An improvement of existing functionality label Nov 4, 2016
@tboerger tboerger added this to the 1.0.0 milestone Nov 4, 2016
@DblK
Copy link
Member

DblK commented Nov 4, 2016

Do you would like to have a huge PR or smaller PR by folder for example?
I saw on lint it misses several comments for each function.

Tell me what you want.

@xinity
Copy link
Contributor

xinity commented Nov 4, 2016

@DblK smaller PR are easier to review :)

so i'd vote for smaller ones

@tboerger
Copy link
Member Author

tboerger commented Nov 4, 2016

👍 for smaller prs, as @xinity said it's better to review

@tboerger
Copy link
Member Author

tboerger commented Nov 4, 2016

But continue with the models, I already started parts within the makefile pr

@lunny
Copy link
Member

lunny commented Nov 29, 2016

Only modules/bindata/bindata.go not be fixed. But that file is generated by go-bindata. Any idea? @tboerger

@tboerger
Copy link
Member Author

Switch to a proper bindata tool like fileb0x (but it doesn't support tags) or go.rice or somehow ignore it

@tboerger
Copy link
Member Author

On the other side, we will drop the bindata from the repo soon, than it's not part of the repo anymore

@lunny
Copy link
Member

lunny commented Nov 29, 2016

But maybe we can ingore the golint check on Makefile at first. So that we an close this issue and ask all the PR to pass the golint.

@tboerger
Copy link
Member Author

Maybe you can filter out the bindata package from the list temporary? Like grep -v

This was referenced Nov 29, 2016
@strk
Copy link
Member

strk commented Nov 29, 2016

@lunny if you find out how to ignore a single file, I'm all for going with it, especially as after a "make" invocation you'd have the bindata.go around and it might be annoying to get those false positives

@tboerger
Copy link
Member Author

On the short term we can simply ignore the entire code.gitea.io/gitea/modules/bindata package.

@lunny
Copy link
Member

lunny commented Nov 29, 2016

So this could be closed via #303

@lunny lunny closed this as completed Nov 29, 2016
@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/enhancement An improvement of existing functionality
Projects
None yet
Development

No branches or pull requests

5 participants