From f0ee99a1cfca801028237503ade899d809e5bc5e Mon Sep 17 00:00:00 2001 From: Stan Girard Date: Mon, 30 Sep 2024 15:49:08 +0200 Subject: [PATCH] feat: update SyncsUser status field to be optional (#3284) The SyncsUser model in sync_models.py now has an optional status field. This change allows for more flexibility in managing user synchronization status. # Description Please include a summary of the changes and the related issue. Please also include relevant motivation and context. ## Checklist before requesting a review Please delete options that are not relevant. - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my code - [ ] I have commented hard-to-understand areas - [ ] I have ideally added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged ## Screenshots (if appropriate): --- backend/api/quivr_api/modules/sync/entity/sync_models.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/backend/api/quivr_api/modules/sync/entity/sync_models.py b/backend/api/quivr_api/modules/sync/entity/sync_models.py index 5f72b2469..0b22cba38 100644 --- a/backend/api/quivr_api/modules/sync/entity/sync_models.py +++ b/backend/api/quivr_api/modules/sync/entity/sync_models.py @@ -59,7 +59,7 @@ class SyncsUser(BaseModel): credentials: dict state: dict additional_data: dict - status: str + status: Optional[str] = None class SyncsActive(BaseModel):