Allow steps to be limited to specific classes #15
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR aims to allow steps to be limited to specific classes which allows you to setup steps for multiple models for example if you have steps for users and teams.
Example Usage:
The above will result in 1 step being available to all classes, and 2 steps being available to the
User
andTeam
classes:Other
classes will only see theNormal Step
.User
classes will both see theNormal Step
andLimited User Step
.Team
classes will both see theNormal Step
andLimited Team Step
.This should be a non breaking change as you are still able to define steps the same as before. Also, when you specify a class, it will merge the class steps and non-class specific steps as seen in the example above.
Solves: #8