Fix/check childRoutes in getRoute

[AinaVendrell]

Remember to tag the PR with WIP tag if it's not ready to be merged.
Reference

Description

The function getRoute now checks if the input matches with a childRoute

Context

Some tests of botonic/core were failing because the function getRoute wasn't checking the childRoutes

Approach taken / Explain the design

Call getRoute recursively to check if the input matches with a childRoute

To documentate / Usage example

Testing

The pull request...

• has unit tests
• has integration tests
• doesn't need tests because... [provide a description]

[ericmarcos]

Sorry, I think I didn't explain well the desired behaviour.
When the router gets a "path payolad", that is, a payload in the format __PATH_PAYLOAD__<path> (for example __PATH_PAYLOAD__initial/step-2) this means that we should ignore lastRoutePath value and simply return the route identified by .

The 3 tests that were skipped shouldn't be changed, they reflect the intended behaviour (notice how you changed the 3rd test to match this implementation).

I think the solution could be very simple: just at the beginning of the processInput function, check if we're dealing with a "path payload" (__PATH_PAYLOAD__<path>) and just go find that ignoring the lastRoutePath. We already have a function getRouteByPath that I think you could reuse. Else, just leave the rest of logic as is.

[ericmarcos]

Nice!