Indentation issue with graphQL mock

[sbrauch]

Describe the bug

When I try to declare a graphQL expect clock with toHaveBeenCalledWith I get this error

When I change to the (wrong) indentation, the test passes

Reproduction

Create a graphQL query and try to mock it with an expect "toHaveBeenCalledWith" block.

Entire test:

`describe("getUserPreferences", () => {
it("fetches user preferences when preferences available", async () => {
(axios.post as any).mockResolvedValue({
data: {
findPreferences: [
{
ldap: "testLdap",
buCode: "testBuCode",
preferenceKey: "testPreferenceKey",
preferenceValue: "testPreferenceValue",
},
],
},
});

const ldap = "testLdap";
const buCode = "testBuCode";

const result = await getUserPreferences(ldap, buCode);

expect(result).toEqual({
  data: {
    findPreferences: [
      {
        ldap: "testLdap",
        buCode: "testBuCode",
        preferenceKey: "testPreferenceKey",
        preferenceValue: "testPreferenceValue",
      },
    ],
  },
});

// PAY ATTENTION TO SPECIAL INDENTATION OF "QUERY" HERE TO MAKE THE TEST PASS
expect(axios.post).toHaveBeenCalledWith("/users/graphql", {
  query: `query findPreferences($ldap: String!, $buCode: String!) {
  findPreferences(ldap: $ldap, buCode: $buCode) {
    ldap
    buCode
    preferenceKey
    preferenceValue
  }
}`,
  variables: { buCode: "testBuCode", ldap: "testLdap" },
});

});`

System Info

Mac OS, vue3 3.4.21, vitest 1.3.1, vite 5.1.5

Used Package Manager

npm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[github-actions]

Hello @sbrauch. Please provide a minimal reproduction using a GitHub repository or StackBlitz (you can also use examples). Issues marked with needs reproduction will be closed if they have no activity within 3 days.