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

Use Guava Splitter to fix StringSplitter warning #2663

Merged
merged 1 commit into from
Jun 2, 2021

Conversation

nastra
Copy link
Contributor

@nastra nastra commented Jun 2, 2021

This code part shouldn't be affected by
https://errorprone.info/bugpattern/StringSplitter as we're checking
explicitly whether the string contains a @ before splitting:
if (path.contains("@")).

@github-actions github-actions bot added the NESSIE label Jun 2, 2021
@nastra nastra force-pushed the suppress-string-splitter-warn branch from 5838618 to c6519a0 Compare June 2, 2021 09:25
@nastra nastra changed the title Suppress StringSplitter warning Use Guava Splitter to fix StringSplitter warning Jun 2, 2021
@nastra nastra force-pushed the suppress-string-splitter-warn branch from c6519a0 to 7375eae Compare June 2, 2021 09:26
Copy link
Contributor

@rymurr rymurr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@rymurr
Copy link
Contributor

rymurr commented Jun 2, 2021

Looks like the CI runs didn't trigger and there are some issues w/ github being reported. Once githubs issues are sorted we should close and reopen this to see if CI is correctly triggered.

@nastra
Copy link
Contributor Author

nastra commented Jun 2, 2021

@rymurr looks like CI was eventually triggered properly and passed

@rymurr rymurr merged commit c821516 into apache:master Jun 2, 2021
@nastra nastra deleted the suppress-string-splitter-warn branch June 2, 2021 12:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants