Flavien Volken

I did not, and you are right enabling it should solve this import problem, but I want to avoid doing so as will break other dependencies of my project ```...

it's interesting to see you opened this issue on TS a year ago :-) and yes, the drawback is that enabling "esModuleInterop" or putting it to true as default is...

@bradzacher nice analyze regarding the comments issue. While doc comments (Double star) are the only one really attached to a class member without any ambiguity, here is how I would...

Oh yes, I can imagine something like this: ``` npm i -g xlayers-cli xlayers-cli --in myFile.sketch --template angular --out ./path/folder ```

You need to add a file containing the directives declarations, for instance, add this file within your GraphQL scope: fake_definition.graphql ```graphql # taken from https://github.com/IvanGoncharov/graphql-faker/blob/2775f1580a6cbe9d2fdf4a823a1374cbbbe3514c/src/fake_definition.ts enum fake__Locale { az cz...

@BendingBender There is the [Nullish](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Nullish_coalescing) operator in JS which makes no distinction between "undefined" and "null". **Optional**: should only mean it can be defined or not (undefined) **Nullable** means it...

I just gave a try and yes… it looks pretty good  I just get a weird error `Type instantiation is excessively deep and possibly infinite.` but the [POC](https://www.typescriptlang.org/play?ts=4.1.0-dev.20200921#code/C4TwDgpgBACgTgezAZxgQ2ACwDwBUoQAewEAdgCbJQIBGAVhAMbBQA+UywcAlqQOYA+KAF4oUAN4AoMWIDaMKLygBrCCAQAzKLgC6ALm3ydBYmUrV6TYNJm2A-FAAGAEnGce-KADJYAX0dsTq7uvHzefgB0rvBIqBg4uEYC-ja2YgYublyh4TApvrL4RCQUVGikILLGDgAUpACuALY0EHDhqupauACUUAYdmto6ANySY+RMADZocNCM08hUAGL1AF6rIADKEDOMCSYl5rQMzIEh-EJSqVCYaCCcaIzKBokj1x3IBud8VaO2SMBuAhSJ8oAAlCAAR3q3Fm5GwK3WWx2cD2EQA8mBAcDkAJRtcHoDGIpkABZDB7GrcEiNL7ZfgAGig0NaIDpHj4TMYaGQEG2IOp3AAbhADDQEAhJjtSN0DA1mq18bZGDiuPVmAg4DVbvdgI9noYdEyPnYDDEUOgsHgBFUmQCgSDTVBERttrtMBisQ7kN0-jJee66hAIOQpU7vrLDaNfOMpjNoKQ0I0IMgwI9oC7ke6JNdeCQ4Bp01BMdiQTm0jJubz+chBSKneLJdK-RXkJrgA2JVLyi2oDGY5IAPSD7Qp4B6MZ51qFxjQTYIZO4cDQKT-egGVcVqDyuVNFpwXu+XuNyZirvN64zOAGWTXWybrf+rjs0K92y+Bl3mSyeX74zDpxf1aKoAnIBAU1IAByFgAHdNWUa43gHSQVRBFg0CXSByAAQTgOA7gMedF2XKoxFEKoUNVKBZmQepJhYURSAgGDnTWV0UUpDDlxwvC7iZWQACIrwiAAGASdG6CIA1RTAagEzAIEmSYEAE7oxjGIA) seems...

The directive declared for faker are only the one related to faker i.e. ```graphql directive @fake( type: fake__Types! options: fake__options = {} locale: fake__Locale ) on FIELD_DEFINITION | SCALAR directive...

Check carefully the included files, you might be importing both a source and a generated .GraphQL file which leads to this duplicated directive error.

In the meantime, I discovered Graphql-box https://www.npmjs.com/package/graphql-box I still did not have time to play with it but it might be a good alternative… at least for the time to...