The WeChat Enterprise API response for getCropCheckinOption() includes a "late_rule" field within the "checkindate" object, but the current WxCpCropCheckinOption class could not deserialize this field because several fields were missing from the data model classes.

Problem

When calling getOaService().getCropCheckinOption(), the API returns JSON with "late_rule" data, but the response object WxCpCropCheckinOption could not access this information due to missing field definitions.

Example API response structure that was failing:

{
 "checkindate": [{
 "late_rule": {
 "offwork_after_time": 3600,
 "onwork_flex_time": 3600,
 "allow_offwork_after_time": true,
 "timerules": [...]
 },
 "allow_flex": false,
 "max_allow_arrive_early": 0,
 "max_allow_arrive_late": 0
 }]
}

Solution

Added missing field definitions to properly deserialize the WeChat API response:

CheckinDate class:

• allow_flex (Boolean)
• late_rule (LateRule object)
• max_allow_arrive_early (Integer)
• max_allow_arrive_late (Integer)

CheckinTime class:

• time_id, earliest_work_sec, latest_work_sec, earliest_off_work_sec, latest_off_work_sec
• rest_begin_time, rest_end_time, allow_rest
• no_need_checkon, no_need_checkoff

LateRule class:

• offwork_after_time (Integer)
• onwork_flex_time (Integer)

Testing

Added comprehensive tests to verify:

• JSON deserialization works correctly with the new fields
• The exact JSON from the issue report can be parsed successfully
• No regressions in existing functionality

The changes are minimal and surgical - only adding missing field definitions without modifying any existing behavior.

Fixes #3323.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.