cy.intercept should provide req.query since the url has the query object

Current behavior

req.url looks like http://hostname:port/?someKey=someValue but req.query is undefined.

Desired behavior

req.url looks like http://hostname:port/?someKey=someValue and req.query is { someKey: 'someValue' }.

Test code to reproduce

cy.intercept({ hostname }, (req) => {
  console.log(req.query) // undefined
  console.log(req.url) // http://hostname:port/?someKey=someValue
})

Versions

Cypress: 7.2.0

[cypress-bot[bot]]

The code for this is done in cypress-io/cypress#16916, but has yet to be released. We’ll update this issue and reference the changelog when it’s released.

[flotwig]

Yeah, I agree that it’s weird to not have query. The only problem with this proposal is that req.url contains the querystring and can be modified, so it stands to reason that req.query can be modified as well. So, if a query property was added, any changes the user makes to it would have to be reconciled with changes to req.url somehow.

IMO the best way to implement this would be to add req.query, but make it just a fancy getter/setter for req.url, so the two can never be out of sync. What do you two think?