It's common to use numeric keycode, especially when we need to access any element of `keyboard.bindings` directly.
Casting to string like:
```
enum KEYS = {
UP: 38,
DOWN: 40,
};
keyboard.addBinding({
key: KEYS.UP.toString(),
// ...
});
```
does *not* work, so `number` should be allowed as well.
* Update CookieAttributes definition to accept SameSite and freeform attributes
* Review feedback: use camelCase, better comment doc, added support for None value
* Including missing array operator on update
* Creating tests for the udpate query completely
* Using Array for infer
* Allowing partial upates
* Using single quotes
* Added collection_method to IInvoiceCreationOptions
* Removed trailing whitespaces
* Fixed review feedback
* Added deprecated tags
* Reintroduced an attribute that is still in use on older versions
* Fixed some alignment issues
according to those specs https://parseplatform.org/Parse-SDK-JS/api/master/Parse.File.html , there are those options:
Valid options are:
useMasterKey: In Cloud Code and Node only, causes the Master Key to be used for this request.
progress: In Browser only, callback for upload progress
This is per the pino docs:
> The destination parameter, at a minimum must be an object with a write method.
Inspecting the source confirms that only a write method (with no particular return type) is required for basic usage: https://github.com/pinojs/pino/blob/master/lib/proto.js#L153. Calls to other potential methods (flush, flushSync, etc) are always guarded with an existence check, as they're not required.
The signature of callbackOrButtons allows either:
1. function that returns void
2. array of AlertButton
Instead the current signature does:
1. function that returns void or an array of AlertButton
This fixes the signature to be correct.
* Fix callback handler inputs
Based on both react-map-gl documentation and trying things out, types
ViewportChangeHandler and ViewStrateChangeHandler both receive a
ViewportProps as input, rather than ViewState as was defined. This
commit fixes that problem.
Fields that were missing include at least 'width' and 'height',
important for working with an auto-resizing map.
* [react-map-gl] ExtraState interface fix
Add missing parameters to ExtraState interface, mark all as optional.
Any or none may be included in a ExtraState object when such is used.
* [react-map-gl] New onViewStateChange inputs
Added new input parameters 'interactionState' and 'oldViewState' to
callbacks 'onViewportChange' and 'onViewStateChange' in
'MapControllerOptions', 'InteractiveMaps' and 'MapContextProps'. There
are also other places where callbacks with similar names are used. But
in those cases, the extra parameters are never used. Because of this,
there are now two different types for callback functions.
* @ember/polyfills: support `undefined`.
Fixes#38681.
* @ember/utils: support JS objects in `typeOf`.
- Fixes#36809.
- Fixestyped-ember/ember-cli-typescript#799
* @ember/debug: add `deprecate` type and tests
Fixes#38682.
* move 'median' tests to separate file
* move 'memoizeWith' tests to separate file
* move 'merge' tests to separate file
* move 'mergeAll' tests to separate file
* move 'mergeDeepLeft' tests to separate file
* move 'mergeDeepRight' tests to separate file
* move 'mergeDeepWith' tests to separate file
* move 'mergeDeepWithKey' tests to separate file
* move 'mergeLeft' tests to separate file
* move 'mergeRight' tests to separate file
* move 'mergeWith' tests to separate file
* move 'mergeWithKey' tests to separate file
* move 'min' tests to separate file
* move 'minBy' tests to separate file
* move 'modulo' tests to separate file
* move 'move' tests to separate file
* move 'multiply' tests to separate file
* move 'nAry' tests to separate file
* move 'negate' tests to separate file
* move 'none' tests to separate file
Brandon Risell