-
-
Notifications
You must be signed in to change notification settings - Fork 726
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
Core
suffix is still used in some settings classes
#3693
Comments
Is this fixed by #3683? |
This fixed by #3683
These are tricky ones because they are both enums in Cake v1.x and we can't use inheritance to keep backwards compatibility as we did with all the different settings classes. So i.e. I'm sure it's possible to change, but I believe it will require updating the underlying runners that are called by the aliases (e.g. I didn't find any other property in any of the new The only usage of |
🎉 This issue has been resolved in version v2.0.0 🎉 The release is available on: Your GitReleaseManager bot 📦🚀 |
Prerequisites
Cake runner
Cake .NET Tool
Cake version
2.0.0-rc0001
Operating system
N/A
Operating system architecture
N/A
CI Server
No response
What are you seeing?
All
DotNet
command settings, still have settings that have properties that contain the wordCore
in them.For example:
DotNetBuildSettings.MSBuildSettings
is of typeDotNet*Core*MSBuildSettings
DotNetBuildSettings.RollForward
is of typeDotNet*Core*RollForward?
DotNetBuildSettings.Verbosity
is of typeDotNet*Core*Verbosity?
This goes for all
DotNet*Settings
related classes.What is expected?
That the
Core
suffix is removed.Steps to Reproduce
Se above
Output log
No response
The text was updated successfully, but these errors were encountered: