larksuite / larksuite/oapi-sdk-python
Python SDK Card object structure is outdated
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 559
- Forks
- 102
- PR merge metrics
- No merged PRs in 30d
Description
the card event json is: body:
{"schema":"2.0","header":{"event_id":"73e49f503b39874de7670ab5b852672c","create_time":"1747740328528651","event_type":"card.action.trigger","tenant_key":"123","app_id":"123"},"event":{"operator":{"tenant_key":"123","open_id":"123","union_id":"123"},"token":"123","action":{"tag":"button"},"host":"im_message","context":{"open_message_id":"123","open_chat_id":"123"}}}
but your python card object has different structure: oapi-sdk-python/lark_oapi/card/model.py at 06c37e71eb5f3176012c7580062bd5230d435149 · larksuite/oapi
All Card object fields are None after the JSON unmarshalling.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with lark_oapi/card/model.py at the linked revision and compare its Card structure with the card event JSON in the issue. Reproduce the JSON unmarshalling behavior and trace why the Card fields remain None. Done means the Python Card object reflects the event structure and its fields are populated after unmarshalling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100