Prettier assumes untagged template string parameter is graphql

Prettier 1.19.1 Playground link

--parser typescript

Input:

function graphql(notgql: string): string {
  return notgql + ' something'
}

const x = graphql(`{id}`)

// following code will cause prettier error: Syntax Error: Unexpected Name "x" (1:1)
// const y = graphql(`x {id}`)

Output:

function graphql(notgql: string): string {
  return notgql + " something";
}

const x = graphql(
  `
    {
      id
    }
  `
);

// following code will cause prettier error: Syntax Error: Unexpected Name "x" (1:1)
// const y = graphql(`x {id}`)

Expected behavior:

The template strings passed to graphql() should not be reformatted because there is no guarantee that they are graphql queries.

[thorn0]

Okay, but calling it a bug is strange, given that it was intentionally implemented in https://github.com/prettier/prettier/issues/2781 as a solution for https://github.com/prettier/prettier/issues/2780. Conceptually, it’s the same feature as formatting tagged templates. As we don’t know how many users rely on this currently, we can’t just remove it, which means it needs configurability. So it’s really the same problem as #5588 / #6626.

[alexander-akait]

@thorn0 Yep, but i think it is not high priority right now