PyCharm won't recognize custom matchers (IE the transform matchers introduced in 0.2.0)
PyCharm will only match on the first matcher used in the file (e.g. first use of use_step_matcher)
To resolve (1) a conditional statement was added to 'fool' PyCharm by having a conditional statement (which will resolve False) to execute use_step_matcher with a non-custom matcher.
To resolve (2) regex actions steps were split to a separate file from parse matcher steps.
Coverage decreased (-0.3%) to 96.044% when pulling 821501622a8fc2b08cc1c2c24ce387374d7565ff on pycharm-matching-patch into f115abcd72eb0152cf82d0f77bc400be32ff61ae on master.
Fixes step matching in PyCharm. Resolves #75
There are two key problems solved here:
use_step_matcher
)To resolve (1) a conditional statement was added to 'fool' PyCharm by having a conditional statement (which will resolve False) to execute
use_step_matcher
with a non-custom matcher.To resolve (2) regex actions steps were split to a separate file from parse matcher steps.