v5.0.0

To support non-UTF8 encoding in paths, the name field changed from String
to OsString in the TrashItem struct. As it's a return value, one won't see
code break unless name is actually used.

Bug Fixes

• Support non-Unicode paths
  There are several spots where paths are assumed to be Unicode. However,
  some (all?) operating systems support non-Unicode paths which causes
  trash-rs to panic if encountered. I switched some of those code to use
  OsStrings instead of Strings. Unfortunately, I had to add a new
  dependency, urlencoding, in order to properly handle decoding non-UTF8
  byte slices.

  As of this commit, the test suite passes and code should be ready, but I
  will try to remove the url crate and use urlencoding in its place
  in the next commit.

Other

• Use objc2-foundation

Bug Fixes (BREAKING)

• Support non-UTF8 paths.
  Note that this changes the type of returned paths to OsString from String,
  hence the breaking change.

Commit Statistics

• 10 commits contributed to the release over the course of 34 calendar days.
• 47 days passed between releases.
• 3 commits were understood as conventional.
• 0 issues like '(#ID)' were seen in commit messages

Commit Details

view details

• Uncategorized
  • Prepare changelog prior to release (02d1a8d)
  • Support non-UTF8 paths. (0971b8f)
  • Update Windows code to account for API change (e4b7119)
  • Simplify Linux/BSD only tests for non-UTF8 paths (559b57b)
  • Impl test for listing invalid UTF8 trash items (209db9d)
  • Cleanup non-Unicode support for readability (2f31116)
  • Remove url and replace with urlencoding (67fb256)
  • Support non-Unicode paths (15a15f8)
  • Merge pull request #107 from madsmtm/objc2 (46585ce)
  • Use objc2-foundation (58b99ef)