Typescript 3.7+ won't compile class generated by client:codegen when Mutation name is same

[rogersp]

Intended outcome:

Typescript 3.7+ can compile classes generated with apollo client:codgen, regardless of how mutations are named.

Actual outcome:

An error occurs during compilation, if the name of the mutation matches the name of the exposed mutation.

For example, when the mutation looks like:

mutation UpdateBook($bookID: ID!, $input: UpdateBook!) {
        UpdateBook(bookID: $bookID, input: $input) {
            ID
            Title
            Author
        }        
    }

Compilation fails with: error TS2440: Import declaration conflicts with local declaration of 'UpdateBook'

However if the mutation name is changed to:

mutation UpdateBookMutation($bookID: ID!, $input: UpdateBook!) {
        UpdateBook(bookID: $bookID, input: $input) {
            ID
            Title
            Author
        }        
    }

The code compiles just fine. Unfortunately I have quite a few existing mutations I would prefer not to rename if possible. Can the generated typescript code use aliased imports?

How to reproduce the issue:

Reproduction case available here: https://github.com/rogersp/apollo-codegen-example

Versions

Typescript 3.7+ (see: https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-7.html#local-and-imported-type-declarations-now-conflict)

Apollo 2.28.0

[rogersp]

This is still an issue with apollo 2.31.1 and typescript 4.0.5. Short of renaming mutations as described above, any suggestions for a workaround?

[rogersp]

Closing this issue for now, was able to migrate over to graphql-code-generator, thanks to #2053