feat(route2): dynamic request aliasing

[flotwig]

TR-369

• Closes Allow dynamically matching requests with a function #387

User facing changelog

• Added the capability to dynamically add aliases for requests intercepted via cy.route2.

Additional details

How has the user experience changed?

PR Tasks

• Have tests been added/updated?
• Has the original issue or this PR been tagged with a release in ZenHub?
• Has a PR for user-facing changes been opened in cypress-documentation? docs(route2): document dynamic request aliasing cypress-documentation#3300
• Have API changes been updated in the type definitions?
• [na] Have new configuration options been added to the cypress.schema.json?

[cypress-bot]

Thanks for taking the time to open a PR!

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.
• Become familiar with the Code Review Checklist for guidelines on coding standards and what needs to be done before a PR can be merged.

[cypress]

---

Test summary

8667 • 0 • 118 • 3

---

Run details

Project	cypress
Status	Passed
Commit	caa820a
Started	Nov 2, 2020 8:54 PM
Ended	Nov 2, 2020 9:06 PM
Duration	11:08 💡
OS	Linux Debian - 10.2
Browser	Multiple

View run in Cypress Dashboard ➡️

---

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard

[flotwig]

this test was duplicated b/t waiting_spec and aliasing_spec

[bahmutov]

question: from the types it seems we can do cy.route2({ url: '/users', alias: 'users' }) right? But there is no test there

[flotwig]

Nope, that's not a thing with this PR. That's the RouteMatcher type, which doesn't have an alias property, since it's supposed to match incoming HTTP requests.

[bahmutov]

super, it will make graphql matching much simpler