Closed rogerfar closed 5 years ago
So that I understand properly, this serializing is not for QuickBooks right? only to recover from your own serialization? It's quite strange that Travis is failing mmm
Sorry I forgot to write that part in!
We serialize both the request and response for transactions we do to a database, which I serialize to JSON first. So yes, it's a nice-to-have really, nothing that has to do with QB serialization.
I'm not sure what Travis is about, it's erroring out on various things, maybe it just has to run again?
Yeah I tried to run it again and it failed once more.
This Travis is driving me quite insane... I build before that PR and it passes fine.
@jsgoupil did you by any chance had a look at this PR? It seems that build was successful at one point: https://travis-ci.org/jsgoupil/quickbooks-sync/requests
The build does not pass anymore... and until we get this figured out, it will mark the whole project as non-passing. I'm going on vacation for 1 week right now.
https://docs.travis-ci.com/user/reference/overview/ Could you add
dist: trusty
in .travis.xml, I think that will fix it.
That seems to do the trick! No rush with this PR, enjoy your holidays!
Published as qbxml-2.1.0 Thanks!
We serialize the request and response objects to QB for debugging purposes, until now if you would send a TimeTracking object the TxnDate would be blank:
I added a few public properties to the DATETYPE object, similar to the DATETIMETYPE object so that when serializing the object it would come out as: