cy.route to match on request body for POST

[cookiescrumbs]

Current behavior:

cy.fixture('teacher/my-library/skills').then((data) => {
    cy.server();
    cy.route({
        url: '/tag/search',
        method: 'POST',
        response: data
});

cy.fixture('teacher/my-library/level').then((data) => {
    cy.server();
    cy.route({
        url: '/tag/search',
        method: 'POST',
        response: data
});

Currently cy.route doesn't match the POST request body which means you can't stub requests that have the same url but a different request body.

Desired behavior:

cy.fixture('teacher/my-library/skills').then((data) => {
    cy.server();
    cy.route({
        url: '/tag/search',
        method: 'POST',
        response: data,
        body: {"filter":{"family":["skills"]}}
});

cy.fixture('teacher/my-library/level').then((data) => {
    cy.server();
    cy.route({
        url: '/tag/search',
        method: 'POST',
        response: data,
        body: {"filter":{"family":["Lesson Type"]}}
});

[SamShiSS]

Same issue here

[jennifer-shehane]

Duplicate of #3248 also - #3333

[cookiescrumbs]

@jennifer-shehane I'm not sure that those are the same as what I'm asking here.
If they are then what is the resolution? Do you have documentation that I could use to stub two post requests with the same url but different requests?

Please could you take another look at my example above and advise on how I might achieve the desired behaviour with the current tools available in cypress.

Thanks

[jennifer-shehane]

@cookiescrumbs Right, sorry, this is different than I was thinking.

Some of this is slightly discussed in this issue #521 but ultimately the functionality that you want is covered in this issue: #387

There are likely some hacky workarounds, especially if you search our issues for graphql, but no way to officially do this through Cypress.

[jlgaustin]

I don't see this in 4.1? Am I missing something or when will this be available?

[cookiescrumbs]

Is there an update on this issue?

[jennifer-shehane]

This functionality has not been released. This is a duplicate issue. Please see #521 or #387 depending on your request.