You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example, document.scrollIntoView should receive object | boolean while PaymentResponse.prototype.details should still be any to allow arbitrary property access. (microsoft/TypeScript#18228)
PS: WebIDL object can be safely mapped to { [x:string]: any }, so we can use it so that both object on function argument and class member can be mapped without any complexity.
The text was updated successfully, but these errors were encountered:
saschanaz
changed the title
Emit object for IDL object type on arguments
Emit { [x:string]: any } for IDL object type on arguments
Sep 15, 2017
RReverser
added a commit
to RReverser/TSJS-lib-generator
that referenced
this issue
Sep 5, 2019
This type on the TS side is relatively new, which is probably why it wasn't used in the first place, but gives more precise definitions and, so, better type checking.
As a side-effect, fixesmicrosoft#290 (although in a different way).
This type on the TS side is relatively new, which is probably why it wasn't used in the first place, but gives more precise definitions and, so, better type checking.
As a side-effect, fixesmicrosoft#290 (although in a different way).
For example,
document.scrollIntoView
should receiveobject | boolean
whilePaymentResponse.prototype.details
should still beany
to allow arbitrary property access. (microsoft/TypeScript#18228)PS: WebIDL
object
can be safely mapped to{ [x:string]: any }
, so we can use it so that bothobject
on function argument and class member can be mapped without any complexity.The text was updated successfully, but these errors were encountered: