Prettier on virtual documents generated by processor

Describe the bug

Codefile with GraphQL operations:

import { gql } from "apollo-server-core";

export const OPERATION = gql`
    query operation($id: ID!) {
        operation(id: $id) {
            id
        }
    }
`;

Prettier try to convert it to:

import { gql } from "apollo-server-core";

export const OPERATION = gql`query operation($id: ID!) {
    operation(id: $id) {
        id
    }
}`;

To Reproduce

.prettierrc.json

{
  "printWidth": 120,
  "overrides": [
    {
      "files": "*.graphql",
      "options": {
        "parser": "graphql"
      }
    }
  ]
}

.eslintrc.json

{
  "root": true,
  "extends": [
    "eslint:recommended",
    "plugin:prettier/recommended"
  ],
  "processor": "@graphql-eslint/graphql",
  "overrides": [
    {
      "files": ["*.graphql"],
      "parser": "@graphql-eslint/eslint-plugin",
      "plugins": ["@graphql-eslint"],
      "rules": {
        "@graphql-eslint/require-id-when-available": ["error"]
      }
    }
  ]
}

Expected behavior

Keep codefile with GraphQL operations:

import { gql } from "apollo-server-core";

export const OPERATION = gql`
    query operation($id: ID!) {
        operation(id: $id) {
            id
        }
    }
`;

Environment:

• OS: Linux 5.10.34-1-lts
• @graphql-eslint/...: 0.9.1
• NodeJS: 14.16.0

Additional context

I will try to explain what I think is happening adding new line characters \n to the document:

import { gql } from "apollo-server-core";\n
\n
export const OPERATION = gql`\n
    query operation($id: ID!) {\n
        operation(id: $id) {\n
            id\n
        }\n
    }\n
`;\n

The @graphql-eslint/eslint-plugin processor extract from “gql`” to “`;” so the generated virtual document begin with a new line:

\n
query operation($id: ID!) {\n
    operation(id: $id) {\n
        id\n
    }\n
}\n

I think is better extract from “gql`\n” to “`;” if the \n exists and my assumptions are correct…

[dotansimha]

Thanks @joual for reporting it, and @B2o5T for the help here! Awesome work 😃 I think we can safely close this one. @xeladejo if you think we need to reopen - just ping me! 😃

[alexojegu]

Yeah, that seems to work fine.

If it were possible to use --fix in the problems detected in virtual documents it would be perfect.

Thanks you.

— EDITED —

The --fix trouble seems happen only on vscode, in the CLI the line is incorrect but it seems to be fixed correctly. I will try to test it better.