Open treping opened 6 years ago
no worry, i follow the structure like you said, so far so good. Thanks!
Okay cool, I added some basic documentation, I'm hoping to have some more time to add depth and examples to it this weekend or next weekend :)
I've added some examples and fleshed out the documentation a bit more. Hope that helps!
Thanks!
Sorry, unfortunately I haven't gotten around to writing up docs/examples yet, made this for work and then had to jump into the next thing :(
If you look at the API Reference for WePay (https://developer.wepay.com/api/), this library follows the same structure in the name spacing. So If you were making a User, you'd use WePay.User.UserService, all the endpoints are functions in this service and the request objects are in WePay.User.Request, the response objects are in WePay.User.Response and all the predefined values used in the request and response objects are in WePay.User.Common. The same goes for Account, Checkout etc.
All of the API endpoints follow this structure and the shared data types are in WePay.Shared.Common, this includes predefined values like currency codes ("USD", "GBP", "CAD"), country codes etc. which are used across different request/response objects from differing API endpoints.
I'm really really sorry if that's not too helpful, I wish I had a bit more time to spend on documentation, I'm hoping to jump back into that soon once I have some more free time. Please let me know if you need anything specific and I can help you out, I can share the code I wrote for our actual integration if that helps as well!