Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[path_provider_windows], [path_provider_linux], [path_provider_platform_interface] update dependencies #3818

Closed
wants to merge 1 commit into from

Conversation

mrquantumoff
Copy link

@mrquantumoff mrquantumoff commented Apr 25, 2023

I updated GNU+Linux, Windows, and platform_interface dependencies, since some of my app's other dependencies were having issues with packages like win32 of v2.0

  • Win32 was 2 majors behind (2.x,3.x)
  • xdg directories weren't on a stable version (not 1.x)
  • some other dependencies weren't using latest possible patches

If you had to change anything in the flutter/tests repo, include a link to the migration guide as per the breaking change policy.

Pre-launch Checklist

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • I read the Tree Hygiene wiki page, which explains my responsibilities.
  • I read and followed the relevant style guides and ran the auto-formatter. (Unlike the flutter/flutter repo, the flutter/packages repo does use dart format.)
  • I signed the CLA.
  • The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
  • I listed at least one issue that this PR fixes in the description above.
  • I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.
  • I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style.
  • I updated/added relevant documentation (doc comments with ///).
  • I added new tests to check the change I am making, or this PR is test-exempt.
  • All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@stuartmorgan
Copy link
Contributor

Thanks for the contribution, but this isn't a change we would accept.

  • Win32 was 2 majors behind (2.x,3.x)

The current version of win32 is 4.x, and the current constraint allows up through 3.x, so it's only one major version behind. #3820 addresses this in a compatible way.

  • xdg directories weren't on a stable version (not 1.x)

1.x is less than 2.0, so is allowed by the current constraint.

  • some other dependencies weren't using latest possible patches

This is a feature for a library; we don't artificially limit what versions of packages people can use.

See also specific notes below.

@@ -5,7 +5,7 @@ issue_tracker: https://github.com/flutter/flutter/issues?q=is%3Aissue+is%3Aopen+
version: 2.1.10

environment:
sdk: ">=2.17.0 <4.0.0"
sdk: ">=2.19.0 <4.0.0"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This would prevent Flutter 3.0 and 3.3 users from using this package, without any benefit.

@@ -16,12 +16,12 @@ flutter:
dartPluginClass: PathProviderLinux

dependencies:
ffi: ">=1.1.2 <3.0.0"
ffi: ">=2.0.1"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This removes compatibility with ffi 1.x without any benefit, creating more potential conflicts in the ecosystem.

path_provider_platform_interface: ^2.0.0
xdg_directories: ">=0.2.0 <2.0.0"
path: ^1.8.2
path_provider_platform_interface: ^2.0.6
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nothing in this package requires these bugfix versions; this artificially prevents clients from using earlier versions if they have a specific need to do so.

xdg_directories: ">=0.2.0 <2.0.0"
path: ^1.8.2
path_provider_platform_interface: ^2.0.6
xdg_directories: ">=1.0.0"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This removes compatibility with version 0.2.0 for no reason (the APIs are identical), creating more potential conflicts in the ecosystem.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All the same comments apply to the other files as well.

win32: ">=2.1.0 <4.0.0"
path: ^1.8.2
path_provider_platform_interface: ^2.0.6
win32: "^4.1.3"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This unnecessarily removes compatibility with win32 2.x and 3.x, creating more potential conflicts in the ecosystem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants