Skip to content

[REFACTOR] Track the remaining TODO-based schema and typing cleanup #1791

Description

@purplesmoke05

Is your feature request related to a problem? Please describe.

The remaining TODO comments are spread across multiple domains such as nullable ORM fields, missing database constraints, response-schema mismatches, and runtime guards added only to compensate for weak typing. If this work is handled without a parent issue, it becomes harder to track progress, define boundaries between related refactors, and confirm when the TODO-driven cleanup is actually complete.

Describe the solution you'd like

Create a parent issue that tracks the remaining TODO-based refactor stream through focused child issues. Each child issue should cover a specific domain, such as Listing nullability, position query guarantees, notification nullability, transfer history invariants, transfer approval datetime cleanup, bond interest payment field normalization, public info schema constraints, and smaller auxiliary model cleanups. The parent issue should be used to monitor progress across those child issues and confirm that the related TODO comments are removed or intentionally rewritten after the refactors are finished.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions