Add duplicate files and companion access token revocation, copy edits

website/src/_posts/2019-10-1.5.md

@@ -1,6 +1,6 @@
 ---
-title: "Uppy 1.5: Issue-busting, cancellation, and new providers"
-date: 2019-10-04
+title: "Uppy 1.5: Facebook and OneDrive (beta) support, upload cancellation"
+date: 2019-10-10
 author: renee
 published: false
 ---
@@ -15,10 +15,19 @@ We are also releasing new remote providers, in beta, for Facebook and OneDrive.
 
 Our issue tracker was getting pretty full over the past year, topping out at about 120 open issues. Some had been open for months without any reply! Issues were opening up faster than our small team could handle, so we sat down to go through everything together and started setting up a process to make sure our issue list doesn't get out of hand again in the future.
 
-When opening a new issue, we ask you to pick whether it's a bug or a feature request, and automatically assign a "Triage" label. If there are many "Triage" issues open at any point, we go through them together in our weekly team call. We now assign issues to a specific team member ASAP, so each of us has a much smaller and more manageable list of issues to keep track of.
+When opening a new issue, we ask you to pick whether it's a bug or a feature request, and automatically assign a “Triage” label. If there are many “Triage” issues open at any point, we go through them together in our weekly team call. We now assign issues to a specific team member ASAP, so each of us has a much smaller and more manageable list of issues to keep track of.
 
 To keep the issue tracker focused on Uppy features and bugs, detailed support questions should go to Transloadit's [community forum](https://community.transloadit.com/).
 
+## Duplicate files
+
+Up until now, if you added a file that has been already added to Uppy sometime before — same `name`/`type`/`modifiedDate` etc — the old file would have been silently replaced with a new one. This changes with v1.5:
+
+1. We now throw a warning if a file with the same `file.id` already exist. New file will not be added, old file will not be replaced.
+2. We are adding the `file.meta.relativePath` to `file.id`. `relativePath` exists on files that have been dropped together with a folder. This means that if you drop a folder with `folder/a.jpg` and `folder/subfolder/a.jpg`, both `a.jpg`s will be added, since they come from different folders and this kind of duplication might be intended.
+
+See PR [#1767](https://github.com/transloadit/uppy/pull/1767) for details.
+
 ## Dashboard
 
 Files in the Dashboard no longer have an icon indicating where they came from (local device, GDrive, etc). We think it's nice for developers to see but not that useful for most end users. If you want to re-enable it, you can add the following CSS to your app:
@@ -29,19 +38,19 @@ Files in the Dashboard no longer have an icon indicating where they came from (l
 The difference is very small. The icons used to be next to the file size, as here in Uppy v1.3:
 ![Uppy Dashboard v1.3, with file source icon](/images/blog/1.5/with-source-icon.png)
 
-Now, in v1.5, it's gone:
+Now, in v1.5, they’re gone:
 ![Uppy Dashboard v1.5, without file source icon](/images/blog/1.5/without-source-icon.png)
 
 Additionally:
-* Editing a file now fires `dashboard:file-edit-start` and `dashboard:file-edit-complete` events (#1776)
-* Excessive debug logging is reduced (#1747)
+* Editing a file now fires `dashboard:file-edit-start` and `dashboard:file-edit-complete` events ([#1776](https://github.com/transloadit/uppy/pull/1776))
+* Excessive debug logging is reduced ([#1747](https://github.com/transloadit/uppy/pull/1747))
 * Fixes to the TypeScript typings were submitted by @mrbatista and @MatthiasKunnen
 
 ## Cancellation
 
 Our old approach to limiting the amount of uploads that could go on simultaneously had some problems. Uploads were queued by chaining Promises, but they did not respect cancellation. So, if you cancelled an upload while some files were still waiting to start, those files would actually start uploading even though they had already been removed. Obviously, that's pretty bad!
 
-PR #1736 addresses this by ripping out the old limiting code, and replacing it with a new, cancellation-aware upload queue. We've also added a browser test to make sure that this thing stays resilient:
+PR [#1736](https://github.com/transloadit/uppy/pull/1736) addresses this by ripping out the old limiting code, and replacing it with a new, cancellation-aware upload queue. We’ve also added a browser test to make sure that this thing stays resilient:
 
 <video alt="Demo video showing an automated Chaos Monkey session with Uppy" muted autoplay loop>
   <source src="/images/blog/1.5/chaos-monkey.webm" type="video/webm">
@@ -50,7 +59,7 @@ PR #1736 addresses this by ripping out the old limiting code, and replacing it w
 
 ## Lerna lerna lerna
 
-In August, we bit the bullet and used lerna's `lerna link convert` feature. Now, all the packages in our monorepo depend on each other using `file:../packagename/` paths, instead of version numbers. The entire repository is one big dependency tree in npm's view. npm can install the entire thing on its own, without `lerna bootstrap`'s help! Since npm manages the entire tree, the `package-lock.json` file in the repository root contains everything we need. We can now use the faster `npm ci` install command on CI, saving over 1 minute on every run :tada:
+In August, we bit the bullet and used Lerna’s `lerna link convert` feature. Now, all the packages in our monorepo depend on each other using `file:../packagename/` paths, instead of version numbers. The entire repository is one big dependency tree in npm's view. npm can install the entire thing on its own, without `lerna bootstrap`’s help! Since npm manages the entire tree, the `package-lock.json` file in the repository root contains everything we need. We can now use the faster `npm ci` install command on CI, saving over 1 minute on every run :tada:
 
 As part of this effort, we also added all our examples to the lerna-managed tree, so you no longer have to do `npm install` in example folders to use them.
 
@@ -61,9 +70,9 @@ npm install
 
 ## Localization
 
-Thanks to multiple contributors, Uppy now knows Czech, Danish, Greek, Indonesian, and Swedish, on top of the 19 languages that were already supported! The Serbian locale is now available in both the Cyrillic and Latin scripts. Big thanks to @achmiral, @arggh, @czj, @jukakoski, @marcusforberg, @nndevstudio, @Pzoco, @Tashows, and @tvaliasek for their efforts :sparkles:
+Thanks to multiple contributors, Uppy now knows Czech, Danish, Greek, Indonesian, and Swedish, on top of the 19 languages that were already supported! The Serbian locale is now available in both the Cyrillic and Latin scripts. Big thanks to @achmiral, @arggh, @czj, @jukakoski, @marcusforberg, @nndevstudio, @Pzoco, @Tashows, and @tvaliasek for their efforts ✨
 
-New translations are rolling in every month, but there are plenty more languages out there that Uppy would love to learn. Please consider [contributing your language](http://localhost:4000/docs/locales/#Contributing-a-new-language) as well!
+New translations are rolling in every month, but there are plenty more languages out there that Uppy would love to learn. Please consider [contributing your language](/docs/locales/#Contributing-a-new-language) as well!
 
 ## Facebook and OneDrive
 
@@ -86,7 +95,7 @@ providerOptions: {
     key: '',
     secret: ''
   },
-  // For OneDrive, use the `microsoft` auth key.
+  // For OneDrive’s key & secret pair, please use `microsoft` option key
   microsoft: {
     key: '',
     secret: ''
@@ -102,13 +111,20 @@ uppy.use(Facebook, { companionUrl: YOUR_COMPANION_URL })
 uppy.use(OneDrive, { companionUrl: YOUR_COMPANION_URL })
 ```
 
-We're still waiting for our developer keys to be approved, so we don't have working examples on the website yet! We'll let you know on [Twitter](https://twitter.com/uppy_io) when they're live.
+We’re still waiting for our developer keys to be approved, so we don't have working examples on the website yet! We’ll let you know on [Twitter](https://twitter.com/uppy_io) when they’re live.
 
 Once these new providers been tested for a while, we'll release them as 1.0 and include them in the main Uppy and Robodog bundles.
 
+## Revoke Companion’s Provider access on logout
+
+Up until now, when users clicked “logout” after using a remote Provider, such as Google Drive or Dropbox, Uppy would destroy the access token. But on the Provider’s side, Uppy was still allowed access. Should the user click “Connect to Google Dtive” again, no extra confirmation was required.
+
+After a discussion in [#1563](https://github.com/transloadit/uppy/issues/1563), we are expanding the logout process. Now when users logout from Google Drive, Instagram, etc, in Uppy, Companion will destroy the token as before, but additionally attempt to revoke the access from the corresponding Provider. In the event that the Provider doesn’t support access revoke via it’s API, Uppy will display a helpful message about how users can revoke the permissions manually.
+
+See [#1843](https://github.com/transloadit/uppy/pull/1843) for details.
+
 ## Misc
 
 * Fill this in
 
 As always, you can find the full list of changes and package versions, as well as future plans, in our [changelog](https://github.com/transloadit/uppy/blob/master/CHANGELOG.md).
-