Skip to content

GH-4517 - Cake Frosting WithCriteria Description #4518

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

Open
wants to merge 4 commits into
base: develop
Choose a base branch
from

Conversation

tstewart65
Copy link
Contributor

Marked the current ShouldRun method obsolete.
Added a new property to IFrostingTask, ShouldRunCriteria which is a List of CakeTaskCriteria. This allows you to have multiple criteria just like what could be done in Cake.Tool.

The current method of the ShouldRun method that you could override and the SkippedMessage has shortcoming when compared to Cake.Tool. First the SkippedMessage could not be set the way it is currently implemented and it only allowed for one message for the task being skipped. It could not be changed if you had multiple criteria to check for skipping a task.

The new ShouldRunCriteria property allows you to setup multiple criteria and have a different message for each one just like Cake.Tool.

This would be nice to have in 5.1 to allow me to continue converting a current cake recipe here at work over to Cake.Frosting. The one downfall is since Cake.Frosting does not support the Spectre Console output the skipped messages are not shown in the summary at this time.

Marked the current ShouldRun method obsolete.
Added a new property to IFrostingTask, ShouldRunCriteria which is a List of CakeTaskCriteria.  This allows you to have multiple criteria just like what could be done in Cake.Tool.
Had removed the ShouldRun method from the tasks but that would be a breaking change.  Forgot to add the check back in to see if it was overridden.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant