Shagen Ogandzhanian
Shagen Ogandzhanian
Let's discuss - idea to be able to easily incorporate existing third-party solutions sounds as a very nice idea. Just to be sure - does csstype provides API for creating...
Marking as testing because in 99.9% percent of cases this affects our pipeline, not real-life scenarios (it's not about code installed via npm install but rather about reading tsonfig.json)
Also it makes sense to support internal attribute.
Let's discuss. It seems to me that we should learn some to deal with such methods somehow other then just ignoring signature declared and substituting by our signatures - just...
It turns out that we already can do this, however may be we don't need to do even that. I'm copying example from the bug reported so we can discuss...
Exception subclasses are generated as typealiases (for the wrong class) instead of proper subclasses
The fact that type aliases might end up in a `@file:JsModule`/ `@file:JsQualifier`-annotated file is a separate bug per se.
Let's discuss. It seems to me that in this particular case we can try to go further and substitute `typeof Something` with just `Something`.
@epabst it looks like comments meta-information is broken in `testData/typeAlias/typeParams.d.kt` Can you please verify on your side as well?
Let's discuss. It's seems to me following options are viable. - Just leave `String | List` because actually the only way those comments are helpful now is as hints -...
Let's discuss - why?