New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

cordova-plugin-file

Package Overview
Dependencies
Maintainers
19
Versions
34
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

cordova-plugin-file - npm Package Compare versions

Comparing version 8.1.2 to 8.1.3

www/ios/Entry.js

2

package.json
{
"name": "cordova-plugin-file",
"version": "8.1.2",
"version": "8.1.3",
"description": "Cordova File Plugin",

@@ -5,0 +5,0 @@ "types": "./types/index.d.ts",

@@ -414,6 +414,8 @@ ---

### v1.0.0
In v1.0.0 of this plugin, the `FileEntry` and `DirectoryEntry` structures have changed,
to be more in line with the published specification.
Previous (pre-1.0.0) versions of the plugin stored the device-absolute-file-location
Previous versions of the plugin stored the device-absolute-file-location
in the `fullPath` property of `Entry` objects. These paths would typically look like

@@ -426,5 +428,3 @@

With v1.0.0, the `fullPath` attribute is the path to the file, _relative to the root of
the HTML filesystem_. So, the above paths would now both be represented by a `FileEntry`
object with a `fullPath` of
Starting with v1.0.0, the `fullPath` attribute is the path to the file, _relative to the root of the HTML filesystem_. So, the above paths would now both be represented by a `FileEntry` object with a `fullPath` of

@@ -438,14 +438,13 @@ /path/to/file

For backwards compatibility, the `resolveLocalFileSystemURL()` method will accept a
device-absolute-path, and will return an `Entry` object corresponding to it, as long as that
file exists within either the `TEMPORARY` or `PERSISTENT` filesystems.
device-absolute-path, and will return an `Entry` object corresponding to it, as long as that file exists within either the `TEMPORARY` or `PERSISTENT` filesystems.
This has particularly been an issue with the File-Transfer plugin, which previously used
device-absolute-paths (and can still accept them). It has been updated to work correctly
with FileSystem URLs, so replacing `entry.fullPath` with `entry.toURL()` should resolve any
issues getting that plugin to work with files on the device.
with FileSystem URLs, so replacing `entry.fullPath` with `entry.toURL()` should resolve any issues getting that plugin to work with files on the device.
In v1.1.0 the return value of `toURL()` was changed (see [CB-6394](https://issues.apache.org/jira/browse/CB-6394))
to return an absolute 'file://' URL. wherever possible. To ensure a 'cdvfile:'-URL you can use `toInternalURL()` now.
This method will now return filesystem URLs of the form
### v1.1.0
Starting with v1.1.0, the return value of `toURL()` was changed (see [CB-6394](https://issues.apache.org/jira/browse/CB-6394))
to return an absolute 'file://' URL. wherever possible. To ensure a 'cdvfile:'-URL you can use `toInternalURL()` now. This method will now return filesystem URLs of the form
cdvfile://localhost/persistent/path/to/file

@@ -455,4 +454,6 @@

In v7.0.0 the return value of `toURL()` for Android was updated to return the absolute `file://` URL when app content is served from the `file://` scheme.
### v7.0.0
Starting in v7.0.0 the return value of `toURL()` for Android was updated to return the absolute `file://` URL when app content is served from the `file://` scheme.
If app content is served from the `http(s)://` scheme, a `cdvfile` formatted URL will be returned instead. The `cdvfile` formatted URL is created from the internal method `toInternalURL()`.

@@ -468,2 +469,9 @@

### v8.0.0
Starting in v8.0.0 the return value of `.toURL()` was changed for iOS to bring
the behaviour more closely to Android. If the webview is hosted on `file://` scheme,
then `.toURL` return will not change and will continue to return a `file://` URI.
Otherwise it will return the app's scheme path.
## cdvfile protocol

@@ -470,0 +478,0 @@

@@ -23,2 +23,13 @@ <!--

### 8.1.3 (Nov 13, 2024)
**Fixes:**
* [GH-642](https://github.com/apache/cordova-plugin-file/pull/642) fix(ios): Entry.toURL() to produce DOM-usable uri when using scheme-hosted webview (#642)
**Tests:**
* [GH-643](https://github.com/apache/cordova-plugin-file/pull/643) fix(test): file.spec.131 moveTo may fail due to read order assumption (#643)
**Docs:**
* [GH-645](https://github.com/apache/cordova-plugin-file/pull/645) docs: Added upgrade notes to `README` for v8 (#645)
### 8.1.2 (Oct 27, 2024)

@@ -25,0 +36,0 @@

Sorry, the diff of this file is not supported yet

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc