* Make last args to quadraticFromPoints optional
Also on cubicFromPoints.
As noted on the docs: https://pomax.github.io/bezierjs/
"The points p1 through p3 are required, all additional arguments are
optional."
* Add updated by
* Add next-redux-saga types
* Add TypeScript version
* Matching TS version of React
* Sort by specific overload
* Fixes after npm run test
* Declare redux dependency
* Statically typed createStore
* For new packages, this file should only "extends": "dtslint/dt.json"
* require(next-redux-saga) is itself a function, not an object with a default property
* Enable ES Module Interop
* df-visible: Fourth argument
Newer version of jquery-visible adds a fourth argument to the jQuery extended method.
* df-visible: added fourth argument test
* allow GraphQLNonNull usage with and without new
* use GraphQLNullableType instead of T on generics of GraphQLNonNull
* fix code-style and add fixes for GraphQLList
4 spaces instead of 2
use `export` instead of `declare`
* add JCMais as definition author
* web3: removed `publicKey` field from Account
* web3: split sign/signTransaction return values to specific interfaces
* web3: `Account.publicKey` removal regression test
* web3: Account.sign & Account.signTransaction regression tests
* web3: fixed typo in web3.eth.accounts.encrypt and added regression test
* web3: added sign(), signTransaction() and encrypt() methods on `Account`
* web3: make linter happy
* Create d.ts file for a11y-dialog.
* Finish up implementation for a11y-dialog.
* Construct unit tests for a11y-dialog.
* added missing create functions.
* tslint successfully passes for a11y-dialog
* Split out constructor for best practices
* none of the duplicates were getters / setters
* Use $ExpectError
Rename some variables
* More typing
* More tests
And update d3-contour
* Add deprecated interface
* Update TypeScript minimal version
Oups :/
* d3-chord TS version update
* Linting errors.
* Strict function type for statistics functions
* Strict function type for histogram
* Update d3-contour
* Ts Lint
* Fix accessor type inference
* Arrays for accessors are ArrayLike, in stat fct
* [jquery] Add detailed deprecation notices.
* [jquery] Add `jQuery.nodeName()`.
* [sizzle] Add named interfaces for `Selectors` properties.
* [jquery] Add `jQuery.expr`.
* [jquery] Add `jQuery.easing`.
* [jquery] Improve formatting of `@deprecated` tags.
WebStorm will not add padding between the description and deprecated text. To improve readability, a zero-width space and space is added to deprecated text to force padding.
VS Code will collapse white space causing detailed deprecation notices to start adjacent to the `@deprecated` tag if there is no header. A minimal header is added where necessary.
WebStorm renders line breaks in JSDoc. This may cause unintentional wrapping of text for `@deprecated` tags. To avoid this, line breaks are not used in deprecated text unless it's intended to render a line break there.
This also fixes broken non-http `@link` tags and ensures that they render consistently.
## Why?
Typescript requires assign of `navigation` on Component that is created with `withNavigation` HOC. But it comes with that function so it shouldn't require that property.
## Example
```typescript
//
// on the current version, this will give an error.
// with this PR, it will work.
//
interface IHelloProps extends Partial<NavigationInjectedProps> {
hello: boolean;
}
const HelloBox: SFC<IHelloProps> = ({ navigation, hello }) => (
<View>
<TouchableHighlightCustom onPress={() => navigation.navigate('TEST', { hello })}>
<Text>Hello</Text>
</TouchableHighlightCustom>
</View>;
);
export default withNavigation(HelloBox);
```
----
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`.)
- [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 adding a new definition:
- [ ] The package does not already provide its own types, or cannot have its `.d.ts` files generated via `--declaration`
- [ ] If this is for an NPM package, match the name. If not, do not conflict with the name of an NPM package.
- [ ] Create it with `dts-gen --dt`, not by basing it on an existing project.
- [ ] `tslint.json` should be present, and `tsconfig.json` should have `noImplicitAny`, `noImplicitThis`, `strictNullChecks`, and `strictFunctionTypes` set to `true`.
If changing an existing definition:
- [ ] Provide a URL to documentation or source code which provides context for the suggested changes: <<url here>>
- [ ] Increase the version number in the header if appropriate.
- [ ] If you are making substantial changes, consider adding a `tslint.json` containing `{ "extends": "dtslint/dt.json" }`.
If removing a declaration:
- [ ] If a package was never on DefinitelyTyped, you don't need to do anything. (If you wrote a package and provided types, you don't need to register it with us.)
- [ ] Delete the package's directory.
- [ ] Add it to `notNeededPackages.json`.
