-
Notifications
You must be signed in to change notification settings - Fork 502
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 static check tests. #3005
Fix static check tests. #3005
Conversation
// | ||
// Note: The function panics if this account doesn't exist in the ledger yet, so | ||
// be sure to fund it before doing this. | ||
func (i *IntegrationTest) EstablishTrustline( |
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 @Shaptic will add later this in a different PR, but for now, since we don't use it, let's remove it.
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.
Yep, this was used in the breaking claiming tests.
@@ -1,3 +1,4 @@ | |||
//lint:file-ignore U1001 Ignore all unused code, staticcheck doesn't understand testify/suite |
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.
In general we don't care about this internal txnbuild
copy - so i removed a bunch of unused files and file-ignore in the new ones. We'll use them as we add more integration tests, but it doesn't really matter since eventually we'll remove these files in favor of the actual txnbuild
PR Checklist
PR Structure
otherwise).
services/friendbot
, orall
ordoc
if the changes are broad or impact manypackages.
Thoroughness
.md
files, etc... affected by this change). Take a look in the
docs
folder for a given service,like this one.
Release planning
needed with deprecations, added features, breaking changes, and DB schema changes.
semver, or if it's mainly a patch change. The PR is targeted at the next
release branch if it's not a patch change.
What
Fixes the CI by removing a bunch of unused code and adding an explicit skip in the places where we know the linter would fail even if the code is being used.
Why
Make CircleCI green again.
Known limitations
[TODO or N/A]