Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
fix(core): matchers should be resetted after unsuccessful matching #46
What kind of change does this PR introduce?
What is the current behavior?
const e1$: Effect = req$ => req$.pipe( matchPath('/test'), matchType('GET'), // ... ); const e2$: Effect = req$ => req$.pipe( matchType('POST'), matchPath('/test'), // ... );
Lets say we have two endpoints which are listening for the same route but with different order of matchers for different methods (POST, GET). If we will send a
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
@@ Coverage Diff @@ ## master #46 +/- ## ===================================== Coverage 100% 100% ===================================== Files 25 25 Lines 297 298 +1 Branches 36 35 -1 ===================================== + Hits 297 298 +1