The tests use them in a way that indicates they are not required, so I
added Partial around reactNativeModal.ModalProps.
This probably resulted from a recent update to react-native-modal.
I submitted a patch previously that added the `raw` function but I
neglected to export the `RawConfig` class, which is what's actually
returned from that `raw` function. My apologies for not getting this
right the first time. Here is the implementation file that shows the
`RawConfig` class and its `resolve()` method: https://github.com/lorenwest/node-config/blob/master/raw.js
* [chart.js] Add weight property to the ChartDataSets interface for Doughnut/Pie charts.
* [chart.js] Run prettier on index.d.ts file.
* [chart.js] Remove all prettier formmating changes.
* Make Marker and InfoWindow components extandable.
Add missing event handlers for marker props.
Add missing methods and variables for Marker and InfoWindow classes.
* Add missing spaces
* Make google variable in MapProps not optional
* Update index.d.ts
Make google, map and marker attributes required for InfoWindow
* [mongodb] Add fix and add watch to db definition
* [mongodb] Add resumeToken member to ChangeStream
* [mongodb] Update doc version in links
* [mongodb] Update link to docs
* [mongodb] allow Binary
* [mongodb] use empty class as ResumeToken
* [mongodb] Update link to watch docs
* Allow registering mixed types of mocks.
* Allow registering mixed types of plugins.
* Update the configuration type.
* Update request operation types.
* Be more specific in plugins' match() signature.
Converts self-referential interfaces to recursive types to work around https://github.com/microsoft/TypeScript/issues/34796
Now that the types _really_ had to be updated for a new version,
there's no longer any reason to keep compatibility definitions for old
versions of TypeScript around, so removed the ones that were already
marked as such. This fixes the types for the as= property.
* [react-relay] Handle all variations of nullability and arrays for `useFragment`
The previous implementation did not detect nullability properly and also missed handling 2 cases for arrays (`[X]!` and `[X!]`).
To do this we always use the `TKey` generic parameter which should be the exact type of `XFragment_foo$key`. Nullability is determined by the type of the `fragmentRef` parameter (the fragment type doesn't actually encode nullability anyway). For arrays the key type will already be an array so we have to handle then slightly differently. We have one overload for each possible combinaison of nullability (2 for regular fields, 4 for arrays).
- Type `ReturnType` is the non-nullable type for a regular field key. Nullability is added on usage.
- Type `NonNullableArrayReturnType` is the non-nullable array type for an array field key. Nullability of the **field** is added on usage.
- Type `NullableArrayReturnType` is the nullable array type for an array field key. Nullability of the **field** is added on usage.
Tested all 6 possible combinaisons of array / nullability with `useFragment<XFragment_foo$key>(...)` and validated that the ts type returned matched the nullability / and whether it's an array of the schema.
* Fix array types
* Add tests, fix nullable array types
* Simplify test key type
* Remove support for array of nullable elements
* Fix lint in example
