Resuming Active "Maintenance" #2
Assignees
Labels
documentation
Improvements or additions to documentation
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Fork Status
Currently this fork has been upgraded to run on PHP 7 and Guzzle 7 with compatability for PHP 5.6 still.
I started a new project and needed to use some of the older APIs which didn't provide OpenAPI spec files. This SDK should now work with Laravel 7 / Guzzle 7 and PHP 7. I may look to provide support for later versions of Laravel/Guzzle/PHP soon.
Endpoint Status(es)
The tooling behind this SDK made by @davidsadler has also been tweaked and fixed to use the moved documentation pages and WDSL URLs to re-generate the following end points:
The above are all WSDL based and reasonably easy to replace with the WDSL2PHP project, however the follow endpoint is a REST based one with no provided OpenAPI or Swagger file, documentation is converted into a wsdl file then processed through xlt templates into PHP code currently, this isn't an ideal situation, but is clever and works!
This end point has been regenerated by collecting the documentation pages and a number of extra fixes added to prevent Types being generated instead of Enums in certain places.
The following API endpoints will no longer be updated on this fork as they are either deprecated by eBay or have been re-generated into new SDK client libraries using the eBay provided OpenAPI Spec files:
I would highly recommend starting to use the newly generated SDKs under the zvps namespace combined with the OAuth section of this package until it gets refactored to it's own package.
At version 20.0.0 the above will be removed from this package, this SDK will be focused on maintaining support for the WSDL based endpoints and PostOrders. The buying API REST SDK clients will be generated from the OpenAPI Spec files soon, selling ones are all done and available.
Future Plans
To keep the WSDL based and PostOrder endpoints updated using the existing method created by @davidsadler.
To move the OAuth endpoint to a separate package for reuse in the new OpenAPI Spec generated API sell/buy REST clients.
To remove replaced end points from here eventually.
PRs
If you have already forked and improved or fixed areas of the SDK which haven't been included yet, please feel free to raise a PR to this repo. As long as they are not on a file marked as automatically generated we should be able to pull these in. If they are to an automatically generated file, we will need to look at the change and implement in the tool which generates these files instead.
OpenAPI Spec SDKs
Under the zVPS org I have generated and listed to packgist the following SDKs using OpenAPI Spec files:
To deal with OAuth and Application token collection i'm still using this SDKs OAuth classes, however as previously mentioned my plan will be to life this out and include / make available when pulling in any of the newer SDKs.
There is a main package available for Sell, the equivalent Buy package will also be available once generated:
This will pull in all the related packages in one go rather than listing all the SDKs in your composer.json, left to make/generate:
Buy APIs left to generate:
Commerce APIs left to generate:
If these new packages and maintained fork starts to see some traction / use I'll look at moving them to a fresh Github Org and bringing in some testing / other maintainers to help.
The text was updated successfully, but these errors were encountered: