You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i'd like to add this awesome library to awesome-go, a curated list of awesome golang libraries and tools. Personally, I use this list quite often to get an overview which libraries exist for a specific topic I want to implement.
They require some quality standards like test coverage and documentation for libraries to be added.
However, gocover.io reports an error when running: strconv.ParseFloat: parsing "": invalid syntax
Are you guys interested in adding this library to the list and look into the error? This can lead some new folk to this library and support development as well as some more attention, which is always good :)
I've read the docs about testing and you write that it isn't that easy to test generated code. Is it possible that the syntax error is occurring due to generated code?
code coverage over generated code is hard. I tried with coveralls but couldn't get it to exclude the generated code. No idea what gocover.io is doing though.
I personally really dislike that golint rule XXX should have comment or be unexported. It leads to useless comments most of the time. At least golint excludes generated files.
Hi,
i'd like to add this awesome library to awesome-go, a curated list of awesome golang libraries and tools. Personally, I use this list quite often to get an overview which libraries exist for a specific topic I want to implement.
They require some quality standards like test coverage and documentation for libraries to be added.
However, gocover.io reports an error when running:
strconv.ParseFloat: parsing "": invalid syntax
Are you guys interested in adding this library to the list and look into the error? This can lead some new folk to this library and support development as well as some more attention, which is always good :)
I've read the docs about testing and you write that it isn't that easy to test generated code. Is it possible that the syntax error is occurring due to generated code?
PR: avelino/awesome-go#2566
Greetings
The text was updated successfully, but these errors were encountered: