Open happyclicker opened 9 months ago
+1, interested in this topic
@paulomarg - Can you speak to this? Thanks!
Hey folks, thanks for bringing this to our attention.
As of late, our team's bandwidth as of late has been taken up by keeping up with the Remix and Rails stacks, and we haven't been able to give the PHP stack the same level of support.
This is on our mind, and we've been internally discussing how we can better serve the PHP community.
We appreciate your patience while we try to find the best path forward. In the meantime, if you run into an issue and find a solution, please create a PR, and we'll focus on reviewing / merging them in a more timely manner - I've improved our tracking of PRs on this repo to help us do better from now on.
Thanks @paulomarg for the response! #315 and #330 would be helpful.
I'll review those and add support for API version 2024-04 soon!
About #315, do you still think it's necessary? We changed the way we set up the PHP version so it doesn't block new versions until v9 in #318, so I'd expect v5.3.0 of the package to just work on 8.3.
I've merged #330, available in v5.4.0 along with the API version.
@paulomarg - Thank you. You're correct, #315 isn't needed anymore.
As of late, our team's bandwidth as of late has been taken up by keeping up with the Remix and Rails stacks, and we haven't been able to give the PHP stack the same level of support.
If we pay more, will Shopify have enough money to afford a few more devs? Perhaps if there is more of that aforementioned 'bandwidth', Shopify would have the resources to include concern for us peasants; who aren't using Remix and Rails. 😄
@paulomarg Thanks for your work here, and your clarification.
However, I just want to point out, that there are a ton of developers who use PHP (more than Rails, anyway) and I think you are losing out on a lot of potential apps and devs if you don't provide proper and up to date packages and libraries
In my humble opinion, I don't think a lot of devs will want to learn Rails just to do a Shopify App, they will just move to platforms where PHP is more welcomed. I'm a 20 years PHP and JS dev, and I don't really see how Rails could be of any use to me outside of here. There are other languages that I could be learning in this time.
See also the issue https://github.com/Shopify/shopify-app-template-php/issues/503 , in your other PHP related repo. As I said there, I think this will bite you in the long run.
Also, I would suggest you switch off the Github Stale Bot on this repo, since all it does is generate useless noise and doesn't help anyone.
Can you perhaps push a new release at least? Last release of this repo is Nov 30, 2021 and I think you have made stable updates since that
For Composer projects, tags will serve as stable tags
This issue is stale because it has been open for 60 days with no activity. It will be closed if no further action occurs in 14 days.
xD xD xD
Well, this is awkward. We've just removed the stale bot so this won't happen any more.
As an update, we're continuing to monitor PRs in this repo, while we work on a long term plan for how we can support PHP apps in the future. Again, thank you for your patience, and for working with us.
@paulomarg I find it a bit odd that a big company such as Shopify does not allocate more resources to maintain their official sdks. Us as developers use these sdks to integrate with Shopify and bring business to them, it's not like maintaing sdks is a waste of funds
Hey everyone. Thank you again for your patience, I wanted to share a bit of an update with you.
We've started to track issues as well as PRs in this repo, and we've gone over existing issues and made sure that we're tracking those as well. We will investigate these issues alongside our other libraries, and for the sake of transparency, it might be a while before we can get to all of them.
We still welcome community PRs if you spot any improvements you'd like to make!
Any update on this from Shopify? The versions supported in the SDK aren't even available in the Shopify documentation anymore.
Seems silly to have to build out our own just to be in keeping with the current API version so that the documentation can be followed properly.
Issue summary
Is this package abandoned?