-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Clean up settings #10655
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
Clean up settings #10655
Conversation
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.
thank you!
That was fast ^^ |
@abgruszecki The failure in "CI for Scala3doc / community-docs" seems spurious. Is it? Or did I actually break something? |
@sjrd it's the compilation that failed, of all things. I'm not sure if the failure is spurious. Did we break CLI API compat? |
6f5b9b7
to
7570c6c
Compare
There is no test covering that setting, and Scala 2.13 does not have it either.
It doesn't do anything on its own, because the code that takes it into account is commented out. Since we have to uncomment it to enable it, there is no point in also having a setting.
As well as the parameter in the `Settings` of staging, which were affecting the value of that setting (to no effect).
We keep -Ysemanticdb as an alias (an "abbreviation") so that we do not break all the existing tools that enable that setting.
7570c6c
to
4bc743e
Compare
I had to take out the rename of |
A first batch.