* webcam: add showVideoSourceDropdown
* webcam: update video device list when adding/removing a video device
* webcam: cleaner changes
* delete extraneous file
* webcam: store sources data in state
* webcam: regather sources after getting access
* webcam: put the source selector next to the buttons
* webcam: put the video source selection on its own row in mobile view
* website: show webcam video source dropdown
* enable webcam features in dev example
* facingMode takes precedence over deviceId, and not needed when specific device is selected
fixes issue where on mobile (iOS) the device selection was ignored due to facingMode being set to 'user'
* Remove “video source” copy, style select, deal with iOS zoom-in issue
Co-authored-by: Tsy-Jon Lau <tlau@parsys.com>
Co-authored-by: Artur Paikin <artur@arturpaikin.com>
The editor is unusable if you're importing stylesheets individually and leave this one out. In line with the documentation of other plugins, I added a note to import the relevant CSS file.
* docs: document Companion 2.0 related changes
* docs: migrating from companion v1 to v2
* docs: correct node version range for companion 2.0
* website[docs]: update minimum node.js requirement for companion
* allow webcam to accept constraints as option
* webcam: add typings for `videoConstraints`
* docs: update docs for the new webcam videoConstraints option
* Update website/src/docs/webcam.md
* webcam: prefer videoConstraints.facingMode over facingMode
* webcam: merge in setOptions
* webcam: handle case where constraints cannot be satisfied
Co-authored-by: Kevin Southworth <kevin.southworth@webascender.com>
* tus: deprecate autoRetry
`autoRetry` retries failed uploads when the user's internet connection
comes back up after an outage. It's not totally clear from the name that
that is what it does: it could also just retry automatically after a
failure generally.
This feature can be implemented by users like this:
```js
uppy.on('back-online', () => {
uppy.retryAll()
})
```
I think that's clearer than `autoRetry: true`, and we don't even have
to come up with a name!
Since the implementation is trivial and the functionality is independent
of tus, it probably shouldn't live in the plugin. Users can copy the
three lines from the docs and use it that way. We could also consider
moving it into `@uppy/core`.
* tus: fill in pr url
* tus: revert runtime deprecation
* changelog: remove deprecated `autoRetry` in 2.0
* [WIP] First pass at adding zoom plugin and zoom companion service for allowing imports from zoom cloud
* WIP. Remove zoom example and move zoom companion code into core companion package, update list endpoint to retrieve based on pagination token or dates available, and get size / download endpoint working.
TO DO:
- fix logout / token expiry
- investigate why test for loading config from file is not working as expected
- confirm pagination works
* Modify provider views to allow for cases with zoom provider when insufficient results exist to enable infinite scroll (but users may need to retrieve older results), update types tests. Linters failing on the provider views files
* Update uppy and companion for the zoom integration to use folders to represent months, and retrieve 1 month at a time.
- clean up code around response data items to explicitly show fields, and match style of other provider methods
- update license date to 2020 across repo
- enable download/uploado of json timeline files
- fix companion test to load credentials from file
- remove front end code no longer required now that folders are being used instead of loading more with button
* Change initial check for user authentication to use same endpoint so we can reuse the same app permission list (ie dont require additional permissions to read user data)
* Clean up zoom provider index file, add api call back to retrieve user account information such as created timestamp and email, fix file icons, remove unused strings, remove license date updates from branch
* Add permission list to grant configurations, remove undefined response body check, update error to match style of other providers, reorder svg attribute to match other icons
* Add request to get user email address for when we are retrieving user meetings and meeting recordings within zoom provider, clean up logout api call
* Update adapter to use meeting UUID when returning the meeting id to match the meeting ID associated with the recording file meeting. This should also resolve issues around reused meeting IDs from zoom.
* Fix companion test
* uppy,robodog: do not add zoom yet
* zoom: add publishConfig
* test: remove uppy.Zoom use from typescript e2e test
Co-authored-by: Renée Kooi <renee@kooi.me>
