* Fix typo Enumberable -> Enumerable
* Set return type to Enumerable of filter, reject etc to support chaining
* findBy value type should be any, not string
* Convert return type for Enumerable to NativeArray<T>
* lodash: _.get should with numeric keys, too.
Also added some better tests.
* lodash: add one more NumericDictionary overload for _.get
* lodash: more reasonable index for _.get tests
* Fix Node's path.format() requiring all options
The bug manifested during use of path.win32 and path.posix submodules.
Both functions required all of the options to exist which is not
the case as some override others.
Further research indicated that previous Node versions were also
susceptible, up to v4.
I've used the Typescript's Partial<> type which makes all properties
optional, allowing for easier maintenance and readabillity at the cost
of now requiring Typescript 2.1, which I believe is a good trade-off.
* Revert the decision to use TS 2.1 in @types/node
Updating Typescript version would require to update
all other types that rely on Node, which may be quite a lot.
Fixing a bug is not a big enough reason to add new version to all
of those packages.
According to official docs the settings for setupMaster settings are just the ClusterSettings.
There is an ClusterSettings interface already but setupMaster function parameters refered to incomplete and unnecessary ClusterSetupMasterSettings. I deleted the ClusterSetupMasterSettings interface and refer to the existing ClusterSettings which are correct.
https://nodejs.org/docs/latest-v8.x/api/cluster.html#cluster_cluster_setupmaster_settings
* Update insight for recent changes
updates the constructor options with `pkg`, which is now preferred over `packageName` and `packageVersion`.
adds `trackEvent()` method
* update insight test
The Ports field is a map of string to _array_ of Ip/Port objects, as you
can see in the docs: https://docs.docker.com/engine/api/v1.32/#operation/ContainerInspect
As a result of this error type checks are not being run. e.g. Doing
`container.inspect().NetworkSettings.Ports['test'][0].BadField` will
compile without error, despite `BadField` to existing in the interface.
* tabs to spaces
* [node] improve typing of query.parse()
* Update according to review:
- Better naming UrlParsedQuery => UrlWithParsedQuery, UrlStringQuery => UrlWithStringQuery
- replace Url type by UrlWithParsedQuery | UrlWithStringQuery
* Re-introduce url.Url as it is used by several other modules.
* [react-infinite-scroller] fix TS2497
I get this error when importing the module with `import * as InfiniteScroll from 'react-infinite-scroller`:
Error:(9, 33) TS2497: Module '".../@types/react-infinite-scroller/index"' resolves to a non-module entity and cannot be imported using this construct.
This PR fixes that error by merging the exported class with an empty namespace.
* revert accidental formatting change
* Update index.d.ts
Since the command property of a GridColumn can be an array of strings, for example:
{ command: ["edit", "destroy"], title: " ", width: "250px" }
The current definition is
command?: GridColumnCommandItem[];
but it should be
command?: (string|GridColumnCommandItem)[];
* Update index.d.ts for Kendo-UI GridColumn definition
Additional update for command property of GridColumn - following documentation at https://docs.telerik.com/kendo-ui/api/jsp/grid/column-commanditem
* recharts: add some missing label definitions to BarProps XAxisProps and YAxisProps
* doc: Link to the recharts documentation regarding the label property in BarProps, XAxisProps and YAxisProps
The following code snippet would work nicely with the fix:
import * as Velocity from 'velocity-animate';
Velocity.animate(...);
Otherwise, TypeScript throws the following error:
TS2307: Cannot find module 'velocity-animate'.
Klaus Meinhardt