- Some of the `render` parameters should've been made optional.
- The export style of the `'next'` module wasn't correct.
- Added some missing static methods to `Head`
- Some readonly properties of `Router` can be `undefined`.
Note that this also means that `'next'` technically needs to be imported
like `import next = require('next');`
* added cordova-plugin-native-keyboard
* updated to conform linting checks
* onSubmit callback is now optional
* added possibility to use an array for the property country in GeocoderComponentRestrictions
* refactor react-overlays into individual modules
also adds correct definitions for some modules whose definitions
were incorretly being imported from react-bootstrap.
(react-bootstrap depends on react-overlays, not the other way around)
* use exported namespace hack instead of default exports
Adds an optional `comments` field to the `Program`, which will be present
if the AST is created with Esprima using the `{ comments: true }` option.
Adds an optional `innerComments` field to `BlockStatement` which will be
present if the AST is created with Esprima using the `{ attachComments: true }`
option, given the following code:
```.js
function foo(n) {
// comments in an empty block are `innerComments`
}
```
Note that though these fields are not specified in the ESTree specification
they extend the support already present in this set of types for
`trailingComments` and `leadingComments`, which are also unspecified.
* Added UnauthorizedError class.
* Updated definition to match gridstack v0.3.0
* Revert "Updated definition to match gridstack v0.3.0"
This reverts commit 2e1f194e68ffd914af08e1f6265cdc7ffb9f44f4.
Commited to wrong branch
* fix(point-in-polygon): Fixed point-in-polygon type declaration
The export format of point-in-polygon did not match the type declaration format.
* Fixed removed definition author
* Remove export as namespace
This particular file was causing me issues with the new typings-2.0 since it doesn't support exporting namespaces from within modules.
* Updating Q to have optional resolves, adding tslint file, fixing tests compilation
* forgot to merge in latest from upstream, replicated the changes into new folder structure
* adding tslint to q
* latest changes to please tslint, but is currently breaking the .all tests - still need to fix
* fixing the reason why the tests was failing, a problem with Typescript trying to decipher the signature of arrays within function arguments that are unionized, updating tslint to ignore those issues
* whoops, messed up header which failed linting
* Adds props to GridTile
* Adds ts line
* Fixes lint array error
Array type using 'T[]' is forbidden for non-simple types. Use 'Array<T>' instead.
* Fixes lint consecutive blank line error
* Fixes whitespace and semicolon lint errors
* Fixes lint whitespace error
Don't use blank line after '{'
* Fixes lint type error
Use an interface instead of a type literal
* Fixes lint interface error
An empty interface is equivalent to `{}`.
* Lint: Replaces var with let
Do not use 'var'
* Lint: Prefer method signature
* Lint: Fixes array type
Array type using 'T[]' is forbidden for non-simple types. Use 'Array<T>'
* Lint: Fixes boolean type
Don't use 'Boolean' as a type. Avoid using the `Boolean` type. Did you mean `boolean`?
* Lint: Ignore unneccesary exports
* Lint : fix errors
* Lint: adds missing semi-colons
* Lint: Removes spaces
* Lint: Ignore no empty interfaces (We could just delete them)
* Lint: Ignore "dt-header" (could remove patch number)
* Lint: Ignore ban-types so we can use Function
* Remove new props that I added
* Fixes var -> let over replacement
* Add typings for Reactable 0.14. Not complete but the stuff provided by the typings have been tested/used quite extensively by myself during the development of ReactPlayer!
* Add two tests (very simple one and a quite sophisticated one which contains all the components i created typings for...)
The AnimatedEvent class's constructor takes in a config parameter of type EventConfig. This config object is passed to shouldUseNativeDriver, which only returns something other than false if useNativeDriver is ever set.
A case when useNativeDriver is set to true is when Animated.Event is used for an Animated.ScrollView's onScroll prop.
https://facebook.github.io/react-native/blog/2017/02/14/using-native-driver-for-animated.html
* update to use redux 3.7.2 anyaction pattern allowing ts 2.4 upgrade
* move away from anyaction concept for router action and location change action. use redux reducer generic to desribe routerReducer
* Refactor some of the definitions for v7
* Add definitions for formValues decorator
* Refactor definitions for Field, Fields, FieldArray, add tests
* Add files to tsconfig
* Fix immutable version of exports
* Clean up the code, change some types
* Add improvement to generic components
* Remove accidentally added files
* Remove conflicting tests file
* Add Rangy Class Applier module type definition
* Make RangyClassApplier extend the options
And allow strings in tagName
* Remove reference path in test file
This should hopefully Make the Build Green Again
* Remove call to unexisting method
This was meant for another PR, and I got things a bit mixed up... (I'll
submit the other PR that adds the missing rangy-core properties when I
have a bit more experience with the whole process of writing type
declarations)
* Incorporate previous contributor's feedback
Thanks for the great feedback 😃