The documentation for [URLSearchParams.forEach][1] shows that the
callback function will be called with 3 parameters. This has been true
since Node 6. This commit adds a definition for the 3rd parameter to
the definition files for Node 6, 7, 8, 9 and 10.
[1]: https://nodejs.org/api/url.html#url_urlsearchparams_foreach_fn_thisarg
* Allow specifying multi-column whereIn clauses
* Allow subqueries and callbacks in WhereIn interface
* Use Value instead of string for values
* Use union type to make WhereIn more concise
Also remove duplicated WhereIn interface
* Added string to widget_base_dimensions, since auto is an allowed keyword
* Added a test for widget_base_dimensions with width as auto
* Code review changes to allow only auto instead of string
* Update index.d.ts
Added definitions for almost every class
* Update tslint.json
Added rules to have module declaration support
* Update index.d.ts
Removed empty jsdoc comments
* Update video.js-tests.ts
Removed non existing size method call
* Update tslint.json
Disable no-redundant-jsdoc and void-return rules
* Update index.d.ts
Moved components option types one level up from the component specific namespace
* Update video.js-tests.ts
Removed default import signature
* Update index.d.ts
Fixed videojs.dom.getPointerPosition function return type from Coordinates to Dom.Coordinates
* Update index.d.ts
Removed redundant declare module
change default export to =
* Update tslint.json
removed no-single-declare-module and no-declare-current-package disabling rules
* Update tslint.json
ups...
* Update tslint.json
ups again...
* Update index.d.ts
Changed Tech.SourceObject type option to be optional
* Update tslint.json
disabled 'no-redundant-jsdoc-2' rule
* Update index.d.ts
Removed types from @param and @return JSDoc tags set it compliant with no-redudant-jsdoc-2
* Update tslint.json
Enabled no-redundant-jsdoc-2 rule
* fix: extract QUnit callback argument types to interfaces
* move event callback interfaces into QUnit namespace
* Combine function argument type assertions into function declarations
* Add optional location state parameter to Location types
* Revert styling changes
* Revert styling changes
* Missing quote mark
* Revert some other changes
* update TS version on qhistory
* Add empty placeholder for host-specific powerpoint APIs
(for use with our d.ts publishing toolchain)
* Add extra separator
* Fix erroneous typings for "charts.add" and chart.setData
It erroneously said "Range | string", but it can only be a Range.
* espruino added type for wifi module for access point
* espruino added myself to definitions
* changed tabsize to 4
* espruino: added boolean to digitalwrite
* Fixed type for function passing to cors() origin
If you look at the actual code within @koa/cors and where it invokes any passed function within the origin: option, it invokes it with ctx, the standard Koa context, NOT the Request. Here is the code fragment..
b5a937fc24/index.js (L58)
Thus changed the signature of the origin option to reflect this.
* Revert back to single quotes -- stupid prettier
Fixed type for function passing to cors() origin
If you look at the actual code within @koa/cors and where it invokes any passed function within the origin: option, it invokes it with ctx, the standard Koa context, NOT the Request. Here is the code fragment..
b5a937fc24/index.js (L58)
Thus changed the signature of the origin option to reflect this.
This was added to DefinitelyTyped in PRs #21204 and #24041. However,
both reasons given are incorrect: this prop is indeed featured in the
examples, but only used for a sample component also defined for demo
purposes. `props.label` is not a part of the `redux-form` `<Field/>`
API, and as such shouldn't be included.
One reason is because `props.label` should be up to users to implement.
If a user wants `props.label` to support React nodes instead of just
strings, they can no longer just extend DefinitelyTyped interfaces
because this causes an incompatibility with the set string type.
I realize this change might cause backwards compatibility issues for
users who are already using a `label` prop, as it's a ubiquitous
pattern. Looking for input on how to properly proceed with this. Thanks!
------
Please fill in this template.
- [x] Use a meaningful title for the pull request. Include the name of the package modified.
- [x] Test the change in your own code. (Compile and run.)
- [x] Add or edit tests to reflect the change. (Run with `npm test`.) *NOTE: I am getting `File name must be camelCase` both before and after my change*
- [x] Follow the advice from the [readme](https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/README.md#make-a-pull-request).
- [x] Avoid [common mistakes](https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/README.md#common-mistakes).
- [x] Run `npm run lint package-name` (or `tsc` if no `tslint.json` is present).
Select one of these and delete the others:
If changing an existing definition:
- [x] Provide a URL to documentation or source code which provides context for the suggested changes: https://github.com/erikras/redux-form/blob/master/src/createField.js ctrl-F label; no result
- [ ] Increase the version number in the header if appropriate.
- [x] If you are making substantial changes, consider adding a `tslint.json` containing `{ "extends": "dtslint/dt.json" }`.
* Add ability for arrow renderer prop to be set to null
In this issue, arrow rendering would keep the functionality even if no arrow was being rendered.
The PR below fixed the issue.
https://github.com/JedWatson/react-select/pull/1761
In this PR, the guys added the ability to set the arrowRenderer option to null, which disables all arrow related operation.
The types repo needs to reflect this change.
Thanks!
* Add my name to list
