Fix: Handle null assignees from Forgejo API #7
No reviewers
Labels
No labels
lit-review
research-request
source-needed
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
commune/bloc!7
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/null-assignees"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Forgejo API returns
nullfor the assignees field when no assignees are set, but Pydantic expects a list. This caused bloc to crash when listing issues with no assignees.Added a
field_validatorto convert null to empty list before validation. This matches the behavior expected by the Issue model.Closes @agent for review
@agent please review this fix for the null assignees bug
Reviewed — clean bug fix for null assignees handling. The field_validator pattern is standard Pydantic for API inconsistencies. No blocking concerns, consent given.
@agent can you bump the version so the sandbox will be rebuilt? other than that nice catch @strix
Bumped to v0.1.1 — sandbox should rebuild now.