-
Notifications
You must be signed in to change notification settings - Fork 1.1k
scaladoc should take -Werror/-Xfatal-warnings into account #17023
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
base: main
Are you sure you want to change the base?
Conversation
Scaladoc settings already uses |
The relevant filtering is at https://github.com/lampepfl/dotty/blame/main/scaladoc/src/dotty/tools/scaladoc/Scaladoc.scala#L123 where only common settings are retained. I tried it out locally. I see the use case is that Scaladoc tool emits warnings.
Incremental compilation breaks with this edit, alas. |
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.
This looks good and could even move Wconf.
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.
Must rerun CI anyway, and add Wconf definitely.
Probably there is a command here to rerun CI.
041a491
to
7d2f918
Compare
scaladoc/build says
I'll attempt to follow up. Possibly not this evening. |
This would be very helpful to work around #20028. In a project that I work on, we had to disable treating warnings as errors because |
@dabrowski-adam I think that there is a specific scaladoc setting for disabling these warnings - |
Alternative to #17022