Fixed Python SDK keys to camelCase.#84
Conversation
Co-authored-by: Divkix <Divkix@users.noreply.github.com>
|
/oc fix the ci |
Co-authored-by: Divkix <Divkix@users.noreply.github.com>
|
I found and fixed three CI issues in the Python SDK workflow ( 1.
|

Done. The root cause was that the Python SDK sent
source_file/line_number(snake_case) in the JSON payload, while the server readssourceFile/lineNumber(camelCase).Changes made:
sdks/python/src/logwell/client.py(lines 114–116)Changed dict keys from
source_file/line_number→sourceFile/lineNumberwhen building the log entry that goes to the queue.sdks/python/src/logwell/types.py(lines 27–28, 36–37)Updated the
LogEntryTypedDict to use camelCase keys so the public API matches the JSON schema the server expects.Tests updated to assert on the new camelCase keys:
tests/conftest.pytests/unit/test_client.pytests/integration/test_e2e.pyThe internal
SourceLocationdataclass still uses snake_case (source_file,line_number) since those are Python attributes and only the wire-format keys needed to change.Verification: All 286 Python SDK unit tests pass.
Closes #55
opencode session | github run