-
Notifications
You must be signed in to change notification settings - Fork 15
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
chore: apply codacy fixes #3935
Conversation
✔️ Code generated!
📊 Benchmark resultsBenchmarks performed on the method using a mock server, the results might not reflect the real-world performance.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Linter as a service
@@ -1,6 +1,6 @@ | |||
module github.com/algolia/algoliasearch-client-go/v4 | |||
|
|||
go 1.21 | |||
go 1.22 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
23 even, no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can people using go1.22 still use this lib if we use 1.23 ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think so yes, as long as we don't depend on std introduced in 1.21+
I guess we should add multi version testing to Go too D:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just tried it with the CTS: go: module ../../../clients/algoliasearch-client-go requires go >= 1.23 (running go 1.22.8)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should stick to a low version
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oki nice then let's keep 1.21 because that's what we settled on at the major release
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks cleaaaan, not sure about Go
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🆗
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
gégé
Co-authored-by: Pierre Millot <[email protected]> Co-authored-by: shortcuts <[email protected]>
algolia/api-clients-automation#3935 Co-authored-by: algolia-bot <[email protected]>
algolia/api-clients-automation#3935 Co-authored-by: algolia-bot <[email protected]>
algolia/api-clients-automation#3935 Co-authored-by: algolia-bot <[email protected]>
🧭 What and Why
We use Codacy to statically analyse the code and find vulnerabilities.