* fix: type definition for cookies.set
The docs explicitly state the omission of `value` will cause the deletion of a cookie. `null` is more explicitly an omission than `""`.
* fix: remove overload which does not exist in the underlying library
* chore: bring tests inline
* Fixed filterPolicty alternative type
* Allow AwsFunction layers property to be defined as key with string so Ref can be used.
* Added optional type to Stream interface
* Update types/serverless/plugins/aws/provider/awsProvider.d.ts
Co-authored-by: Frédéric Barthelet <fredericb@theodo.fr>
* Update types/serverless/plugins/aws/provider/awsProvider.d.ts
Co-authored-by: Frédéric Barthelet <fredericb@theodo.fr>
* Update types/serverless/plugins/aws/provider/awsProvider.d.ts
* Update awsProvider.d.ts
Added missing semicolon
* awsProvider.d.ts
Formatted document
Used Array<> syntax for AwsFunction.layers
* Fixed SNS filterPolicy test
Co-authored-by: Frédéric Barthelet <fredericb@theodo.fr>
* Fixed missing support for allowSpecialUseDomain
* Fixed unexpected path mapping
* Added overload for findCookies
* Updated all types to be in line with the current state of the package
* * Fixes that all types that extend Asset should be accessed via the Asset namespace.
* This is technically a breaking change, but only of previously erroneous typings.
* Therefore, along with moving the handful of interfaces that weren't in the Asset namespace into it, I've included another large test script -- face-in-video-controller.ts -- to verify these corrected typings.
* Improves the typing of SceneObject's getComponent and getComponents so the return values are correctly typed if the string passed in is a literal.
* Improves the typing of Component.ScriptComponent so that the script input and api typings are easily defined by extending the SnapchatLensStudio.ScriptInputs and SnapchatLensStudio.ScriptApi interfaces, providing an example of how to do so.
* Documents for the `Pass` interface how to extend it for the various possible Shader Properties, which are not documented as necessarily being available or not on the Pass type in Snapchat's API documentation https://lensstudio.snapchat.com/api/classes/Pass/ in spite of all examples involving it assuming they do exist.
* Restores the `files` tsconfig.json property.
* Fleshes out the following interfaces that were incomplete in @julien-c's initial type definitions (I hadn't noticed till I started using them - and added a test for the same):
* Transform
* Material
* Refactors the existing tests to take advantage of the typing improvements for the Component.ScriptComponent's ScriptInputs and ScriptApi interfaces
* Adding @mhwinkler as an author on this.
* Makes the coords of the vec2, vec3, vec4, quat, and vec4b optional (as they actually are)
* Reverts the last change; those arguments are *not* optional. (It was the MathLib classes that have those optional parameters, not the system ones.)
* Slight comment instructions copy update
* Added missing toGeoJSON to AbstractGeometry
* Test added
* Used object vs Object
* Removed extra lines
* More space formatting
Co-authored-by: Tyler Gray <wtgray@hirequest.com>
* @types/auto-sni: update tests
* @types/auto-sni: update type to allow callback for domains option
* fix(@types/auto-sni): add parentheses
* fix(@types/auto-sni): update test
* feat(@types/auto-sni): add dir option
* feat(@types/auto-sni): add dir to test
* Add rest operator and array type handling for omit-deep-lodash
* Update version
* Revert "Update version"
This reverts commit 50ef98f9f8e229d36c5cc5d277fe4a3a1ce8973d.
* [react-router-config] Allow custom route config type
I am working in a codebase where we extend the route object with
some custom properties. To make this work with TypeScript, we need
to be able to specify a custom route config type. This commit
expands the generics here to allow this to be threaded through the
types in a backwards-compatible way.
* Run Prettier on react-router-config files
The diff included a lot of things that I hadn't touched in my previous
commit, so I decided to do this as its own commit to make it easier to
review.
* Update index.d.ts
The property `originalPosition` was missing in the `DraggableEventUIParams` type
* Update index.d.ts
* Add test
* Update index.d.ts
Typescript issues an error if a function is tested without subsequently
being used. So I added some obviously-ignored uses of the tested
functions in the chrome-apps tests.
