Currently the step lookup algorithm just enumerates all available step
definitions until it finds a match. This isn't particularly optimised,
but appears to be how it's implemented in cucumber-ruby.
It also doesn't handle ambiguity (multiple step definitions matching a
step name), but that can be saved for another day.
sharplet
commented
9 years ago
:sparkles:
Currently the step lookup algorithm just enumerates all available step definitions until it finds a match. This isn't particularly optimised, but appears to be how it's implemented in cucumber-ruby.
It also doesn't handle ambiguity (multiple step definitions matching a step name), but that can be saved for another day.
Fixes #6.