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

[RFC]: Support for PSR-6 & PSR-16 v3 #133

Closed
boesing opened this issue Jul 27, 2021 · 1 comment · Fixed by #275
Closed

[RFC]: Support for PSR-6 & PSR-16 v3 #133

boesing opened this issue Jul 27, 2021 · 1 comment · Fixed by #275

Comments

@boesing
Copy link
Member

boesing commented Jul 27, 2021

Feature Request

Q A
New Feature yes
BC Break no

Summary

PSR-6 and PSR-16 has v2 & v3 available. Since I dont see the point of supporting v2 AND v3, we should be fine with supporting v1 and v3.
We could use composer/deprecated-package-versions along with an autoload check for the psr/cache version to use class_alias to provide support for both v1 & v3 of psr/cache and psr/simple-cache.

Same compatibility layer is used in laminas/laminas-cli to support both symfony/console v4 & v5.

We could also use composer-runtime-api requirement but I am not yet fully convinced that anyone is able to use composer in v2 but I am open for this change, if the majority is fine with having a hard requirement to the composer-runtime-api.

@boesing boesing added this to the 4.0.0 milestone Jul 30, 2021
@boesing boesing changed the title Support for PSR-6 v3 Support for PSR-6 & PSR-16 v3 Nov 22, 2021
@boesing boesing changed the title Support for PSR-6 & PSR-16 v3 [RFC]: Support for PSR-6 & PSR-16 v3 Nov 22, 2021
@boesing boesing linked a pull request Nov 11, 2022 that will close this issue
@boesing
Copy link
Member Author

boesing commented Aug 29, 2023

Closed with #275

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

Successfully merging a pull request may close this issue.

1 participant