DEVEXP-589 Added docs for rows feature #40
Conversation
Will tackle eval in a separate PR, had a lot to add with this one.
| | `xml` | XML document defining the columns and rows. | | ||
| | `csv` | CSV text with the first row defining the columns. | | ||
| | `json-seq` | A [line-delimited JSON sequence](https://datatracker.ietf.org/doc/html/rfc7464) with the first row defining the columns. | | ||
| | `mixed` | TODO Seems like we should remove this as it does the same thing as "return_response". | |
There was a problem hiding this comment.
@BillFarber See my note here - thoughts on removing this? I doubt it would ever be used, and return_response=True would be the more consistent way to just get the original multipart/mixed response back.
There was a problem hiding this comment.
If 'mixed' just has the same affect as "return_response=true", then I would remove it.
However, would it work and be useful to use Client.process_multipart_mixed_response(response) to pre-process requests with the 'mixed' format?
There was a problem hiding this comment.
Not that I know of yet, and in fact, one reason I'd like to move the eval stuff out of client.py is so that the process_multipart... method isn't yet public. While it may be useful in the future as a public method, we don't know that yet, and I lean towards making things non-public when in doubt (as opposed to what I did with e.g. ml-app-deployer).
BillFarber
left a comment
BillFarber
left a comment
There was a problem hiding this comment.
It's fine with me if you want to remove 'mixed' first.
Will keep it here, and likely remove in a separate PR. |
Will tackle eval in a separate PR, had a lot to add with this one.