Jason Judge

Actually, you do already detect and parse the JSON. However, the JSON for GB Payroll is a very different structure to the XML versions of AU/US Payroll. It has a...

The contention for the JSON field names is `lowerCammelCase`, so even where the field names are the same as the AU payroll API, they still need their letter case changed.

Oh yes, fun and games. What I'm not sure about yet, is whether the two JSON formats can be parsed together with one set of rules that covers the fields...

I think I understand the old paging now. There never was a `pagination` object to tell you how many records there are, how big the page is, what page you...

Xero put GB on hold while they focused on fixing up the AU payroll. Our project is on hold while they do that. Hopefully it will start up again later...

I believe (through the grapevine) the `page=N` `GET` parameter has been (or is being) introduced for pagination of payroll records. It may not have reached the documentation yet. To get...

@jeremyj11 Xero recently tried to create swagger files for their APIs, and that led to the realisation, final acceptance and admission of just how horribly inconsistent the APIs are ;-)...

`Calcinai\XeroPHP` ;-) There would be a lot of changes, but hopefully they would all be simple replacements in file headers. Maybe there is an IDE that can move a namespace...

Yeah. why not. I created an organisation "academe" in github, named after my company, and put loads of stuff in there. The org then feeds into other areas such as...

To illustrate further, in a service I created a cache item with this package and read it using the laravel cache: ```php $cacheItem = new \Madewithlove\IlluminatePsrCacheBridge\Laravel\CacheItem('xyz'); $cacheItem->set('foobar') $this->cacheItemPool->save($cacheItem); dump(\Cache::get('xyz')); ```...