docs: breaking changes for moveItemToTrash (#25286)

This commit is contained in:
Jeremy Rose 2020-09-03 12:44:16 -07:00 committed by GitHub
parent 4dc09ea9dc
commit d305fe7d30
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -12,6 +12,20 @@ This document uses the following convention to categorize breaking changes:
- **Deprecated:** An API was marked as deprecated. The API will continue to function, but will emit a deprecation warning, and will be removed in a future release. - **Deprecated:** An API was marked as deprecated. The API will continue to function, but will emit a deprecation warning, and will be removed in a future release.
- **Removed:** An API or feature was removed, and is no longer supported by Electron. - **Removed:** An API or feature was removed, and is no longer supported by Electron.
## Planned Breaking API Changes (13.0)
### Removed: `shell.moveItemToTrash()`
The deprecated synchronous `shell.moveItemToTrash()` API has been removed. Use
the asynchronous `shell.trashItem()` instead.
```js
// Removed in Electron 13
shell.moveItemToTrash(path)
// Replace with
shell.trashItem(path).then(/* ... */)
```
## Planned Breaking API Changes (12.0) ## Planned Breaking API Changes (12.0)
### Default Changed: `contextIsolation` defaults to `true` ### Default Changed: `contextIsolation` defaults to `true`
@ -50,6 +64,18 @@ If your crash ingestion server does not support compressed payloads, you can
turn off compression by specifying `{ compress: false }` in the crash reporter turn off compression by specifying `{ compress: false }` in the crash reporter
options. options.
### Deprecated: `shell.moveItemToTrash()`
The synchronous `shell.moveItemToTrash()` has been replaced by the new,
asynchronous `shell.trashItem()`.
```js
// Deprecated in Electron 12
shell.moveItemToTrash(path)
// Replace with
shell.trashItem(path).then(/* ... */)
```
## Planned Breaking API Changes (11.0) ## Planned Breaking API Changes (11.0)
There are no breaking changes planned for 11.0. There are no breaking changes planned for 11.0.