v0.12.0
Fixed
- HTTP 200 with an
{"error": ...}body is no longer reported as success.
Story tables requested before the story calculation has run, and design checks
whose preconditions aren't met, report the refusal under a 2xx status. These now
raiseMidasResultError. PassMidasClient(raise_on_result_error=False)to get
the raw body back instead. - Non-JSON responses stay inside the SDK's exception hierarchy. A proxy or
SSL-inspection appliance answering with HTML used to raise a raw
JSONDecodeErrorpastexcept MidasAPIError; it now maps to a typed error,
keepingMidasAuthErrorfor an intercepted 401. DbResource.items()no longer raisesAttributeErroron empty tables.
A zero-row response can come back as{"message": ""};items()returns{}.midas_nx.__version__matches the installed distribution. It had reported
0.10.0since v0.11.0.
Added
post.base.unwrap_table()— finds theHEAD/DATAtable in a/post/TABLE
response by shape. The top-level key is not stable across sessions, so indexing
byTABLE_NAMEis unsafe.MidasResultError, exported frommidas_nx.
Compatibility
get_table()'s return value is unchanged. The one behaviour change is the
MidasResultError raise described above.