Using graphql-tag inside an Angular Component throws duplicated fragment/query error

Describe the bug Here’s a bug repository: https://github.com/kroeder/angular-gql-gen-bug-repro-repo

If you use gql`...` inside an angular component then gql-gen fails with the message

  > gql-gen

  √ Parse configuration
  > Generate outputs
  > Generate src/__generated/types.ts
  √ Load GraphQL schemas
  √ Load GraphQL documents
  × Generate
  → Found 2 errors in your documents


    We found 1 errors

    Failed to generate src/__generated/types.ts

    Found 2 errors.
    GraphQL Code Generator validated your GraphQL documents against the schema.
    Please fix following errors and run codegen again:

  ./src/app/app.component.ts:
    There can be only one fragment named "VoteFields".

  ./src/app/app.component.ts:
    There can be only one fragment named "VoteFields".

This does not work

@Component({
  selector: 'app-root',
  templateUrl: './app.component.html',
  styleUrls: ['./app.component.css']
})
export class AppComponent {
  thisFragmentDoesNotWork = gql`
    fragment VoteFields on Vote {
      vote_value
    }
  `;
}

This does work

const outsideFragmentWorks = gql`
  fragment VoteFields on Vote {
    vote_value
  }
`;

@Component({
  selector: 'app-root',
  templateUrl: './app.component.html',
  styleUrls: ['./app.component.css']
})
export class AppComponent {
  thisFragmentWorks = outsideFragmentWorks;
  orThisOneAsWell = gql`
    ${outsideFragmentWorks}
  `;
}

To Reproduce Steps to reproduce the behavior:

1. Checkout https://github.com/kroeder/angular-gql-gen-bug-repro-repo
2. npm i
3. npm run gql-gen
4. Play around with https://github.com/kroeder/angular-gql-gen-bug-repro-repo/blob/master/src/app/app.component.ts

Expected behavior Should work. Altough I’m not sure if this is a gql-gen or graphql-tag issue

Schema/Documents Already inside the repo

Environment:

• OS: Windows 10
• Codegen:

    "graphql-code-generator": "^0.14.5",
    "graphql-codegen-typescript-client": "^0.14.5",
    "graphql-codegen-typescript-common": "^0.14.5",

• Node:

$ node --version
v10.13.0

[kamilkisiela]

@dotansimha I guess since v0.15.0 was released we can close this one

[kroeder]

Works fine with 0.15.0-alpha.6d689c5d Thanks!