* Updated @feathersjs/socket-commons
* Fixed linting errors.
* Added type definitions for hook-less service methods.
* Revert "Added type definitions for hook-less service methods."
This reverts commit 14e8062a57f68b7c338ee092fb3e5cfea9e6f226.
See https://github.com/DefinitelyTyped/DefinitelyTyped/pull/34684
* Adds namespace in loadableReady
* Adds type for namespace option in loadable server
* Updates version number in header
* Bumps up the version of loadable__server
I've added type definitions for the new account.business_profile and
account.settings fields introduced in API version 2019-02-19. There are
still some other account props that remain undefined.
For reference: https://stripe.com/docs/upgrades#2019-02-19
* Types for the mixed.notType function.
* move notType only to 'LocaleObject'
* fix delete 'label' property
* fix to 'strict-export-declare-modifiers' rule
* added test from MixedSchema
* export interfaces FormatErrorParams and LocaleValue
* fix(expo): mark `initialize` parameter property as optional
* Also extracts the parameter's type to an interface for clarity.
* style(expo): move the methods that are related close to each others
* refactor(expo): simplify the `alias` signature
* fix(expo): fix invalid signature of `getEnabledAsync` and `setEnabledAsync`
* docs(expo): update the contributors list
* [aws-lambda] Keys should be optional inside CloudFrontHeaders
According to the AWS documentation, it is optional to specify a `key` for each header value, but the type declaration is currently requiring this to be specified unnecessarily.
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/lambda-event-structure.html#lambda-event-structure-response
> - `key` (optional) is the case-sensitive name of the header as it appears in an HTTP request; for example, `accept` or `host`.
> - If you do not include the header key portion of the key-value pair, Lambda@Edge will automatically insert a header key using the header name that you provide. Regardless of how you've formatted the header name, the header key that is inserted automatically will be formatted with initial capitalization for each part, separated by hyphens (-).
>
> For example, you can add a header like the following, without a header key: `'content-type': [{ value: 'text/html;charset=UTF-8' }]`. In this example, Lambda@Edge creates the following header key: `Content-Type`.
By making this property optional, one is able to write:
```ts
import { CloudFrontHeaders } from 'aws-lambda';
const headers: CloudFrontHeaders = {
'content-type': [{ value: 'text/plain '}],
};
```
... instead of having to repeat the header name like:
```ts
import { CloudFrontHeaders } from 'aws-lambda';
const headers: CloudFrontHeaders = {
'content-type': [{ key: 'content-type', value: 'text/plain '}],
};
```
* Update test
Setting a header without specifying the key should not raise a TypeScript compiler error.
* Revert "Update test"
This reverts commit 088653e362e6f0a152f54e9b5694bb778b072354.
* Add test for AWSLambda.CloudFrontHeaders with and without explicit keys
* updated types to match the newest version of react-image-crop
updated tests
added missing semicolon
reverted minimum ts version
* Made crop optional, and renamed resolveCropAndTriggerChange to resolveCrop
* type definition for fundamental-react
* removing my co-author to make definitelytyped-header-parser happy
* fixing issues to make travis happy :)
* onClick index is mandatory now
* similar folder structure
* making sure, all files are used
* removed an import that is not provided by fundamental-react
* trying to convince travis, that all files are necessary
* fixed a typo
* included index files in tsconfig.json
* fixed formatting
c4605
