- Implemented models for nodes usage history including NodeInfoDto, GetUserAccessibleNodesResponse, and usage statistics.
- Created subscription-related models such as UserSubscription, SubscriptionInfoData, and various response DTOs for subscription information.
- Developed models for subscription settings, templates, and system statistics, enhancing the API's capability to manage and retrieve subscription configurations.
- Introduced user management models including CreateUserRequestDto, UpdateUserRequestDto, and various response DTOs for user actions.
- Added bulk actions for user updates and statistics tracking, improving the efficiency of user management operations.
- Established a base controller for handling API requests and responses, along with decorators for HTTP methods to streamline API interactions.
- Included utility functions for serialization using orjson for better performance with Pydantic models.
- Updated models and response structures to align with API v2.0.0 specifications.
- Enhanced response handling to support both wrapped and unwrapped API responses.
- Added new controllers for ConfigProfiles, InternalSquads, InfraBilling, and NodesUsageHistory.
- Implemented RootModel patterns for list responses, allowing direct iteration and indexing.
- Updated tests to validate new models and endpoints, ensuring 20 out of 21 tests pass with real API integration.
- Fixed various bugs related to response handling and model validation.
- Documented migration path and breaking changes for users upgrading from v1.x to v2.0.0.
- Implemented TemplateResponseDto and UpdateTemplateRequestDto for subscription templates.
- Created models for system statistics including CPU, memory, and bandwidth.
- Developed user models for user creation, updates, and responses.
- Added bulk actions for user updates and statistics tracking.
- Introduced tests for authentication, bandwidth statistics, hosts, inbounds, key generation, nodes, subscriptions, and user management.
- Enhanced utility functions for generating random strings, emails, and date ranges for testing.
