fix(models): restore check_in/check_out on AvailabilityQuery #20

Merged
padreug merged 1 commit from fix/availability-query-fields into main 2026-09-21 09:03:32 +00:00
Owner

v0.4.0 shipped with AvailabilityQuery missing its check_in/check_out fields: my merge of public_booking_dict landed inside the class and left the two lines orphaned after the helper's return. POST /api/v1/availability raised on q.check_in, a 500 on every install of that version. The RPC door reads the raw body and was unaffected, which is why nothing noticed; the live test ran against an uncommitted tree that was correct.

Fix restores the fields and adds a test that constructs the model and drives the endpoint. To be released as v0.4.1 straight away.

v0.4.0 shipped with AvailabilityQuery missing its check_in/check_out fields: my merge of public_booking_dict landed inside the class and left the two lines orphaned after the helper's return. POST /api/v1/availability raised on q.check_in, a 500 on every install of that version. The RPC door reads the raw body and was unaffected, which is why nothing noticed; the live test ran against an uncommitted tree that was correct. Fix restores the fields and adds a test that constructs the model and drives the endpoint. To be released as v0.4.1 straight away.
v0.4.0's merge of public_booking_dict landed inside AvailabilityQuery and
left the two date fields orphaned after the helper's return, so
POST /api/v1/availability raised AttributeError on q.check_in (500) on
every install of that version. The RPC door reads the raw body and was
unaffected, which is why nothing noticed.

Put the helper next to public_room_dict and add a regression test that
constructs the query model and drives the endpoint through the
services layer.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
padreug deleted branch fix/availability-query-fields 2026-09-21 09:03:32 +00:00
padreug referenced this pull request from a commit 2026-09-21 09:06:35 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
aiolabs/chatelet!20
No description provided.