Open jankonas opened 3 months ago
I am currently doing more Kubernetes stuff than programming so I do not want to maintain any new libraries. But if neomerx/cors-psr7
is dead and someone (you) are willing to start maintaining a fork, I am ok switching to it.
Thank for the reply. I created an issue in the neomerx/cors-psr7
repository.
As for maintaining my fork, I have no problem with that, I would just have to sort out some infrastructure stuff (for now it's just a mirror from a private Gitlab repository) to ease accepting the PRs and issues.
In the meantime, I submitted #90, feel free to close it if you don't want an untestable stuff in your repository.
I would like to use this package with
psr/http-message
v 2.x. I could easily provide PR with update tocomposer.json
to allow it, but there is a problem withneomerx/cors-psr7
which seems to be no longer maintained.In my projects i use my fork which replaces the original package, so adding
|^2.0
tocomposer.json
would be enough for me, but keeping theneomerx/cors-psr7
dependency would mean that this package will be never tested againstpsr/http-message
v 2.x.What are your thoughts about this package future? Are you willing switch to some
neomerx/cors-psr7
fork or fork it yourself?