On the dashboard, when uploading a folder, if files from that folder are not successfully added, the count would still say they are there
For example, If you're using Google Drive, and upload a folder with 3 images and 2 mp3 files. If you also have a restriction set to only allow images, Dashboard would still read something like "5 Files Added", even though only 3 would be there. I resolved this by making the `addFile` method in the `provider-views` package return a boolean value based on whether or not the file was added successfully. I then created a count variable with the `addFolder` method and added to that count for every successful addition. Using that count instead of the total count of files in the folder fixes this problem
Resolves#2038
* 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
In #2239, I added a backwards compatible implementation for the `resume`
option from tus-js-client v1, but forgot to disable it again in the
Transloadit plugin.
Fixes#2382
* [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>
I added support to load thumbnails when uploading AVIF images, by adding 'avif' to the regex. I also updated the unit test.
Note that support for this is dependant on browser support, and currently only Chrome 85+ and Firefox 77+ support it (Firefox requires flag to be set to allow it)
