-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
[BUG] "superseded" means the old thing #57919
Comments
The only thing that uses it is the As the styles are mutually-exclusive, the state could be written to support both (and warn on the old one), without any need for a config option. The misnamed option can then simply be deleted. |
I just learned that @meaksh implemented a compatibility layer that can automatically handle the differences between the |
That's a slightly different approach - it detects what it "should" be, and converts the input to be that. Or, given it's been deprecated for a while, the old style could simply be dropped, and the config option along with it. |
I support removing the option (the other issues discussing the module.run disambiguity are 👍 ), since 1) it's mis-named, and 2) it's not useful. That should be done as part of the module.run silliness. |
The option was removed in 3005. |
Therefore the config option
use_superseded
has the opposite meaning to what it does.The text was updated successfully, but these errors were encountered: