Breaking change: v8.2.0 returns only file name in path property, not the path
See original GitHub issue- I found a bug
- I want to propose a feature
What is the current behavior?
The files Objects returned on onDrop
used to return the entire file path in the path
property. Sinse v8.2.0 not any more.
What is the expected behavior?
The path
property should contain the entire path, just as it does in v8.1.0.
Returning only the file name is an undeclared breaking change. And it makes no sense as the path
property now returns exactly the same data as the name
property.
Our usage of Dropzone depends on the entire path being returned: Our app only saves the full path as url. It does nothing with the files themselves.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:11
Top Results From Across the Web
Breaking Changes | Electron
This document uses the following convention to categorize breaking changes: API Changed: An API was changed in such a way that code that...
Read more >Migrating to 8.0 | Elasticsearch Guide [8.5] | Elastic
At startup, Elasticsearch will automatically migrate the data path to the new layout. This automatic migration will not proceed if the data path...
Read more >Path.GetFileName Method (System.IO) - Microsoft Learn
Returns the file name and extension of a file path that is represented by a read-only character span.
Read more >Migration Guide | Cypress Documentation
Migrating to Cypress 12.0 This guide details the changes and how to change your code to migrate to Cypress version 12.0.
Read more >Process | Node.js v19.3.0 Documentation
js process will terminate. The listener callback function is invoked with the exit code specified either by the process.exitCode property, or the exitCode ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@Shaker-Hamdi It is not solved. I am still stuck on v8.1.0 😦
The reason this issue is closed is that the issue seems to be in file-selector, see here: https://github.com/react-dropzone/file-selector/issues/10
I am consistently getting this behavior in versions 11 to 14 again when using tauri. See: https://github.com/react-dropzone/file-selector/issues/10#issuecomment-1170136347