* [react-table]: V7 upgrade to support rc-16
Support the changes in
https://github.com/tannerlinsley/react-table/blob/master/CHANGELOG.md
Most of this in internal, by far the biggest user facing ripple is
flatColumns -> allColumns.
* add selectSubRows option
* remove column.show - no longer supported
* add className to TableCommonProps
* fix missing import, doh
* remove afters from ensurePluginOrder, it's effectively removed
* Update Hook definitions as well as address review comments
I've made a good effort to fix the types for the hooks, they look right,
but right now I have no code that uses them so they are at best
theoretical based on how they appear to be used in the code.
* add type definitions for https://www.npmjs.com/package/rtp-parser
* added test for payloadTypesHash
* make a generic version of the parseRtpPayloadType
* fixed some typos
* add test for generic number payload types
* use-generics-for-express-response-type: Use generics for Response in express
* use-generics-for-express-response-type: fixing ghost-storage-base-tests
* Added AuthProvider, user._isLinked, user._unlinkFrom, User.logInWith, User._registerAuthenticationProvider. Changed signature of user.linkWith to match the one in the Parse.User documentation
* Added tests for changed and added types
* Added changes to TS 3.7 as well
* Removed deprecated _linkWith from TS 3.7 definitions
Jason Clark <https://github.com/riceboyler> has offered to help maintain
this package and offered a good PR overlapping with the current open PR
which he then closed. But it showed a good approach to the solution and
demonstrated an understanding of the problem space.
* urijs: Correct UMD typings, remove implicit global.
* urijs: add case for testing implicit global var in a script
* urijs: Add test to test UMD global in an ES module
* urijs: Undo unnecessary reformatting
* [aws-lambda] Deprecate CustomAuthorizer*, new APIGateway*Authorizer*
Noticed this testing #42419.
When integrating a custom authorizer, you actually have two options,
creating a token or a request authorizer, which changes what payload
you will get. You nearly certainly know which you will be called with!
Just deprecating the old version as it's kinda broken in a way thats
hard to fix without breaking someone, but we want to guide devs to the
new version.
It is possible to fix the existing type by adding a bunch of
`foo?: never` fields to each alternative so existing accesses don't,
error but this makes things more complex, and confusing for the common
case.
Other ideas welcome!
* [aws-lambda] Add api-gateway authorizer parameters.
Fixes#34069, #42418
Ended up a bit messy, might be a bit much.
* [aws-lambda] Bump minimum typescript to 3.0
Required to fix failing $ExpectError in tests.
Surely nobody is still using pre-3.0?
* [aws-lambda] Enforcea API Gateway authorizer context narrowing
And implement the changes that API gateway does on the proxy request context for it.
Also rename TAuthorizer to TAuthorizerContext to be more clear that they should be the same type across both authorizer and proxy.
Some cleanups and fixes for names.
Andrew Casey