* Added possibility of specifying form field type.
* remove log statements
* Change to allow providing custom render function
* Add Types and Docs.
* Pass Uppy-styled CSS class names, so developers can leverege them when adding their custom inputs
@goto-bus-stop as we’ve discussed, what do you think?
* Fix var name
* dashboard: make typings for `render()` stricter
so people will get type errors if they try to return React elements or
raw DOM nodes.
Co-authored-by: Artur Paikin <artur@arturpaikin.com>
Co-authored-by: Renée Kooi <renee@kooi.me>
* Fix fragment URL
The hashtag: "#Configure-Standalone" is not correct and doesn't lead to anything. Fixed that.
* Update website/src/docs/companion.md
* Apply suggestions from code review
Co-authored-by: Artur Paikin <artur@arturpaikin.com>
* webcam: request a video mime type listed in `allowedFileTypes`
* webcam: stop recording when we are about to reach the max file size
* webcam: request an image mime type listed in `allowedFileTypes`
* docs: add Webcam#preferredImageMimeType
* locale: add `recordingStoppedMaxSize` string
* changelog: check webcam restrictions
Co-authored-by: Artur Paikin <artur@arturpaikin.com>
* Add meta.relativePath explicit example
Spent hours to test it to add a relativePath and non unique ids for files with the same name but coming from different folders.
It works like it but it's confusing with the `setMeta` method.
* tweak comment
Co-authored-by: Renée Kooi <renee@kooi.me>
* Fix translations that did not respect word order
Fixes#2069
We were still using raw string concatenation in these two places. To
maintain backwards compatibility, this commit adds _new_ translations
that are substitution-based instead of concatenation-based. The old
translation is passed in as a possible substitution parameter
`backwardsCompat`, and the default (English) translations use this
parameter.
With this, if you are using a custom locale that overrides eg. the
`exceedsSize` string, Uppy will first get your `exceedsSize`
translation, and then use the default `exceedsSize2` translation which
concatenates that result and the file size. So it works the same as it
did in the past.
If a translation requires a different word order, it can override the
`exceedsSize2` translation instead.
```js
new Uppy({
locale: {
strings: {
exceedsSize2: 'Maximum file size of %{size} exceeded',
poweredBy2: '%{uppy} made this!'
}
}
})
```
In 2.0, we can remove all the old strings and only use `poweredBy2` (and
probably rename them to `poweredBy` too, heh)
* website: add missing dashboard strings to docs
* locales: remove unused second plural form from EN and NL
* build: allow different numbers of plural forms
* utils: add test for new throwing behaviour
* docs: insert PR url
* locales: revert ko_KR changes
* changelog: add 2.0 backlog entry
* locales: var → const
* docs: add brief note that translators should supply a pluralize function
* locales: update en_US with new template
* fix HEIGHT_MD = 400
Co-authored-by: Artur Paikin <artur@arturpaikin.com>
* 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
