add forStepClass method to get state more convenient #108
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.
Hi,
This
forStepClass
is similar to theforStep
method to get the state for a specific step, but it uses a component class, which is not the component name. So it could be easy to autocomplete by the IDE, or in case we have many component registries in a package for long names likepackage:namespace.feature.steps.options-step
.And by the way the name of the Step component registered in the service provider is used nowhere in view, so sometimes it could leak to an error when trying to refactor the class component, tho.
This is an addition, so there is no breaking change