Added additional properties that were missing
Changed CalendarEvent to type any, since this could be anything based on what the user is using for their event
Added specific types for View, Navigate, Format
Updated other types and functions that were incorrect with the current version of the package.
Two changes:
1) We are now allowing the parameters of a request to be typed. This
adds more type safety to consumers.
2) We support optional parameters in the request.
For (2), the root cause is this issue in how Typescript handles
--strictNullChecking:
https://github.com/Microsoft/TypeScript/issues/9235
* @types/ws: Update types definition for ws@4.0
* @types/ws Update type definition for ws@4.0
- Change extensions attribute type
- Rename headers event to upgrade
* @types/ws - Updage ws tests to be in sync with ws@4.0.0
* missing comment
* missing comment
* add iteratee property shorthand for uniq in underscore
* undo bad commit
* can also pass array of array of data to chartist
* First update to bring the mongodb typings to version 3
* Updated tsconfig of the older v2 version
* Set mongodb version to 2 in packages with errors
* MongoClient extends form EventEmitter
* Added bar.space as an optional property to ChartConfiguration interface
This property lets you to set space between bars in bar charts
* Add tests for new property
* @types/sequelize Added generic types for various option classes
* Revert "@types/sequelize Added generic types for various option classes (#22755)"
This reverts commit 38983ce
* Make react-loadable export an assignment
`react-loadable` does *not* actually have a default export. This can be shown
by running:
```
> var L = require('react-loadable')
undefined
> L
{ [Function: Loadable]
Map: [Function: LoadableMap],
Capture:
{ [Function: Capture]
propTypes: { report: [Function: bound checkType] },
childContextTypes: { loadable: [Function: bound checkType] } },
preloadAll: [Function],
preloadReady: [Function] }
```
As a result, when attempting to use this with commonjs modules, an error error
is thrown when `allowSyntheticDefaultExports` is set.
```
TypeError: react_loadable_1.default is not a function
```
This PR exports the module as an assignment, so now `import * as Loadable from
'react-loadable'` should be used to import the module.
I am not entirely sure that I have used the best pattern for typings here; but
my goal was to export the proper assignment yet still allow all of the
namespace to be accessible via `(i.e.) Loadable.LoadingComponentProps`. If there
is a better way, please let me know and I will be happy to adjust!
* Use import assignment in react-loadable tests
[WebAuthn](https://w3c.github.io/webauthn/) builds upon the Credential
Management API and provides for origin-scoped, public-key credentials.
It replaces the FIDO U2F API which is currently used to implement this.
While the webauthn spec is still only a candidate recommendation, the
types in this change are sufficient to exercise basic functionality with
Firefox Nightly. (Note: that requires changes in about:config to enable
this API.)
I remove this export to avoid the error error TS2309: An export assignment cannot be used in a module with other exported elements.
Sorry @Mohamed Hegazy that I have to change it again, I didn't get this error before when I tested.
* [joi] make return type of validate() as promise like
* [joi] update "Definitions by" section of the package header.
* [joi] test promise functionality of valdate()
Park Geon