* feat(algoliasearch): rewrite almost completely
Changes are mainly:
1. now has a `lite.d.ts` file for `algoliasearch/lite`
2. fix some of the options in settings and queries
3. specify more result types
* chore: update version number
* chore: fix things by copying, pasting, and removing
* test: remove header
* chore: move to folder, it maybe helps
* [browser-sync] Type definition for Option type is missing many valid properties.
Also appending tests to cover newly added properties/interfaces.
* Updated types and appended some.
The proxy.proxyRes property could be further expressed to take one or three parameters. Its previous representation was not correct according to the documentation and default configuration the package generates.
Specified types for watchEvents, open, and logLevel options.
Converted type Object references to object per recommended guidelines of DefinitelyTyped repo.
Converted type Function references to arrow function.
More SnippetOptions properties, defined FormsOptions under GhostOptions.
Added and modified tests.
* Fixed PermissionType
Added references to cameraRoll and systemBrightness to PermissionType as well as adding userFaceingNotifications and reminders which were missing entirely. Also sorted the constants and the types.
* Fixed linting
There was a trailing white space I left.
* Added to tests
Added the new permissions to the tests.
* Add optional fn parameter on onReady
This callback is executed if provided when the $translate service is ready.
* Add Gabriel Gil to angular-translate definitors
At the moment, this snippet:
```ts
const spawnArgs: ReadonlyArray<string> = ['foo', 'bar'];
spawn('foobar', spawnArgs);
```
fails with:
```
Argument of type 'ReadonlyArray<string>' is not assignable to parameter of type 'string[] | undefined'.
Type 'ReadonlyArray<string>' is not assignable to type 'string[]'.
```
Looking at https://github.com/nodejs/node/blob/master/lib/child_process.js#L514-L535 and https://github.com/nodejs/node/blob/master/lib/internal/child_process.js#L286, it _looks_ like there is no mutation of the array. I am no expert so I'd be happy to be proven wrong, I just couldn't find sufficient evidence that a `ReadonlyArray` wouldn't be fine.
This is not a breaking change because passing a `string[]` is still valid.
* test changes for v3.0
check onClick for spreading the div props support
* Version ReactSVG V3.0 typings
-added myself to contribution list
-added intersection typing with react div typing
* Just kidding these are the real V3 typings
* more changes --> more test changes
This brings the definition in line with official AngularJS packages like
angular-sanitize, angular-mock, and angular-route.
This reference was causing bizzarre path issues when trying to run the
dgeni documentation tool on a project that included these types, and it
appears that the fix for that is to remove the reference, which
coincidentally matches what the official AngularJS packages do.
