* companion: drop parallel down/upload for S3 multipart
We were not ending the `fs-tail-stream` correctly. `fs-tail-stream` is
also not a battle-tested package and relying on file watching is never a
fun time, so it's better if we can avoid it entirely.
One good way to do that is to axe the entire parallel download/upload
feature, and instead download files in full before uploading them, like
we do for Tus and XHR :)
Fixes#1457.
* companion: add back the multiple start calls test
* companion: don't log redundant errors in production
cc @kvz
* companion: remove redundant condition
* companion: if the error is a URIError from the requested URL we only log the error message
* companion: allow providing any S3 option, closes#1388
Now you can configure any S3 option listed in
https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/S3.html#constructor-property.
It adds a warning about the official S3 names `accessKeyId` and
`secretAccessKey` because you should use the Companion-style names `key`
and `secret` instead.
* companion: use awsClientOptions property for Aws SDK config
* companion: also reject keys inside awsClientOptions
* should keep the checks next to each other
* companion: first check if awsClientOptions isnt null
* Update react-dragdrop.md
DragDrop component only accept `uppy` and `locale` props according to the type declared.
```
import { Uppy, Locale } from './CommonTypes';
export interface DragDropProps {
uppy: Uppy;
locale?: Locale;
}
/**
* React component that renders an area in which files can be dropped to be
* uploaded.
*/
declare const DragDrop: React.ComponentType<DragDropProps>;
export default DragDrop;```
* drag-drop: accept a number for width/height
* docs: add back dragdrop props
* docs: use the same option style as previously [skip ci]
Co-authored-by: Renée Kooi <renee@kooi.me>
* types: stronger typings
* Remove remaining `declare module` things for uppy.use
* Format types standard-style-like
* Add `target` properties to plugin typings
* Add type for `replaceTargetContent` option
* xhr-upload: allow lowercase method
* opt in to stricter typechecks
* use the strictly typed version in all typings tests
* endtoend: use strict types in typescript test
* Add some comments to the typings file so IDEs will warn about untyped use()
* informer: remove obsolete option from typings
* react: generate prop types based on actual options types
* react: update types
* react: fix import in typings test
* companion-client: add `pluginId` property to ProviderOptions type
Co-Authored-By: Ifedapo .A. Olarewaju <ifedapoolarewaju@gmail.com>
* core: remove some `any` types
* *: add locale string types
* *: generate locale typings
* core: fix LocaleStrings<> type
* dashboard: add locale string type tests
* tus: inherit options typings from tus-js-client
* transloadit: add missing options types
* ci: do the required build steps before testing typings
* Support TokenStorage in types, add `title?: string` options
* form: update typings
* types: put TokenStorage type in dependents
* Document Uppy.StrictTypes
* if we pin at least we should use the latest
* Allow document.querySelector
I think it's a eslint-plugin-compat bug that it's marking querySelector
as not available in Android Chrome 78.
Co-authored-by: Ifedapo .A. Olarewaju <ifedapoolarewaju@gmail.com>
* Display a browser alrert when an error question mark button is clicked
Informer can dissappear, while the alert dialog will stay on screen indefinitely. Plus it’s easier to copy/paste from the alert, than the bubble (virtually impossible).
* Keep displaying Informer when the message ? bubble is hovered
* Tweak line-height
