Closed dominickj-tdi closed 5 years ago
changesIn
and postChangesIn
are designed for to be able streaming responses if a connection is continuous or eventsource. So the response is sending partially and there is no ability to parse it more concrete early, before closing connection. I left these methods as if. In future, they may change.
Fixes #9
I have updated most of the methods to return the correct response type by default, by including conversion in the various class methods, as we discussed in the referenced issue.
There are two methods I didn't touch because I'm not 100% sure how they work and didn't want to break things. These are
DatabaseModel.changesIn()
andDatabaseModel.postChangesIn()
. Someone more familiar with these methods should probably change those.