Skip to content
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

Closed
2 tasks done
patriksvensson opened this issue Nov 8, 2021 · 3 comments · Fixed by #3696
Closed
2 tasks done

Core suffix is still used in some settings classes #3693

patriksvensson opened this issue Nov 8, 2021 · 3 comments · Fixed by #3696
Assignees
Labels
Milestone

Comments

@patriksvensson
Copy link
Member

Prerequisites

  • I have written a descriptive issue title
  • I have searched issues to ensure it has not already been reported

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 word Core in them.

For example:

DotNetBuildSettings.MSBuildSettings is of type DotNet*Core*MSBuildSettings
DotNetBuildSettings.RollForward is of type DotNet*Core*RollForward?
DotNetBuildSettings.Verbosity is of type DotNet*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

@patriksvensson patriksvensson added this to the v2.0.0 milestone Nov 8, 2021
@devlead
Copy link
Member

devlead commented Nov 8, 2021

Is this fixed by #3683?

@augustoproiete
Copy link
Member

DotNetBuildSettings.MSBuildSettings is of type DotNet*Core*MSBuildSettings

This fixed by #3683


DotNetBuildSettings.RollForward is of type DotNet*Core*RollForward?
DotNetBuildSettings.Verbosity is of type DotNet*Core*Verbosity?

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 DotNetRollForward is just syntactic sugar to allow you to use the new name (without the Core).

i.e. DotNetRollForward.Major is the same as DotNetCoreRollForward.Major

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. DotNetCoreRunner), and possibly add some "smart enum" implementation with implicit conversion, etc. to maintain backwards compatibility 🤔 . I'll do some tinkering.


I didn't find any other property in any of the new DotNet***Settings other than the above - let me know if I missed anything.

The only usage of DotNetCore*** other than the above are the runners that are used by the aliases, and some settings classes that inherit DotNetCore***Settings for backwards compatibility with generic base classes like ToolSetings<T>, etc..

@augustoproiete augustoproiete self-assigned this Nov 13, 2021
augustoproiete added a commit to augustoproiete-forks/cake-build--cake that referenced this issue Nov 13, 2021
augustoproiete added a commit to augustoproiete-forks/cake-build--cake that referenced this issue Nov 14, 2021
augustoproiete added a commit to augustoproiete-forks/cake-build--cake that referenced this issue Nov 14, 2021
augustoproiete added a commit to augustoproiete-forks/cake-build--cake that referenced this issue Nov 14, 2021
@cake-build-bot
Copy link

🎉 This issue has been resolved in version v2.0.0 🎉

The release is available on:

Your GitReleaseManager bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants