We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This relates to wartremover/wartremover#410
Given that there is no way to annotate imports, maybe OldTime should not be warning about them, but only about usage sites.
OldTime
import java.util.Date // wartremover error here. how to whitelist it? @SuppressWarnings(Array(Warts.OldTime)) class X { def y = legacyJavaApi.z(new Date) }
The text was updated successfully, but these errors were encountered:
That should be easy, will try to find time to address it.
Sorry, something went wrong.
Do not check for old Date/Time classes in imports
afe5d74
Please refer to issue wartremover#22
I only notice this now it's no longer a problem, but a workaround would probably be to move the import in to more local scope inside an annotation.
Do not check for old Date/Time classes in imports (#23)
d827e1e
Please refer to issue #22
Scala 2/3 issues warnings with origin to indicate the bad import selector. Tools could do the same if necessary. That enables suppression via -Wconf.
origin
-Wconf
amanjpro
No branches or pull requests
This relates to wartremover/wartremover#410
Given that there is no way to annotate imports, maybe
OldTime
should not be warning about them, but only about usage sites.The text was updated successfully, but these errors were encountered: