-
Notifications
You must be signed in to change notification settings - Fork 17
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
SBT: treat warnings as errors #273
Conversation
@tgodzik two issues, any thoughts? i haven't been able to figure out where this is coming from:
and this comes from the pprint copy, looks like the previous
|
We could ignore those via Wconf like in metals:
https://github.com/scalameta/metals/blob/main/build.sbt#L154 I am digging into the other issue. |
Ach, wait, I thought it's scalameta/scalameta repo 😅 Looks like TypeRepr is a type alias for Type, which is why that is failing. We should switch the cases around |
The other issue is that mdoc depends on metaconfig and metaconfig-docs depend on metaconfig also obviously. But that module is just for documentation, so we can safely turn of that warning via exclude or just ignoring it. Do you want me to finish this PR? |
i thought so, too, but then it looked like you simply copied this code from somewhere... was it fixed there? maybe the fix is not to switch them around but to remove the second case? |
Yes, please!!! |
import metaconfig.Configured.NotOk | ||
import metaconfig.Configured.Ok |
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.
minor, feel free to skip all of this comment:
- i'd add a blank line after package
- i'd import as a wildcard
metaconfig.Configured._
or i'd simply use case Configured.Xxx(...)
below, like they did before, without adding imports.
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.
done
thank you for helping with this. one practical question: how did you manage to push changes into my fork, to continue with this pr? |
I think that' a default option to allow contributors to push to the specific branch. |
No description provided.