state: add trainingStore,modelStore. update: userStore

[codypharm]

Description

• Relates feat: integrate stores to modelTrain flow #130

Checklist

• I have followed the repository's contribution guidelines.
• I have added necessary documentation or updated existing documentation.
• My code follows the established code style and formatting of the project.
• I have tested my changes and they function as expected.
• I have added suitable unit tests (if applicable).

To be reviewed by: @Nasfame @techyNonso

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
app-decenterai-com	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 13, 2023 8:43pm

[codypharm]

Let's get on a call later cos I don't understand what you are saying.

…

On Sat, Nov 11, 2023, 9:58 PM Hiro ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In src/state/modelStore.ts <#138 (comment)> : > @@ -0,0 +1,74 @@ +import { create } from 'zustand' +import { devtools, persist } from 'zustand/middleware' +import { upsert_user } from ***@***.***/explore/upsert_user' +import { Model, TrainingRequest } from ***@***.***/client' + +type IModel = Omit<Omit<Model, 'createdAt'>, 'updatedAt'> +type ITrainRequest = Omit<Omit<TrainingRequest, 'createdAt'>, 'updatedAt'> + +type Store = { + model: IModel | null type Store = { user: IUser | null init: (user: IUser) => void setUser: (user: Partial<IUser>) => void } refer the store above its maintaining user state and keeping it in sync with "user" collection in DB Similarily for every collection in mongoDB, there should be a store. It should be like: the stores are our primariy DB and the changes are replicated to mongoDB ------------------------------ In src/state/modelStore.ts <#138 (comment)> : > @@ -0,0 +1,74 @@ +import { create } from 'zustand' +import { devtools, persist } from 'zustand/middleware' +import { upsert_user } from ***@***.***/explore/upsert_user' +import { Model, TrainingRequest } from ***@***.***/client' + +type IModel = Omit<Omit<Model, 'createdAt'>, 'updatedAt'> +type ITrainRequest = Omit<Omit<TrainingRequest, 'createdAt'>, 'updatedAt'> + +type Store = { + model: IModel | null so there needs to be separate *trainRequest* Store ------------------------------ In src/state/modelStore.ts <#138 (comment)> : > @@ -0,0 +1,74 @@ +import { create } from 'zustand' +import { devtools, persist } from 'zustand/middleware' +import { upsert_user } from ***@***.***/explore/upsert_user' +import { Model, TrainingRequest } from ***@***.***/client' + +type IModel = Omit<Omit<Model, 'createdAt'>, 'updatedAt'> +type ITrainRequest = Omit<Omit<TrainingRequest, 'createdAt'>, 'updatedAt'> + +type Store = { + model: IModel | null for ModelStore: on init: it should get all models of userId from DB. Don't use : models: IModel[] | null It becomes harder to access. Use an object : {modelID: model} Good job on creating: model: IModel | null to maintain the state of DB-unsynced model. It does raise concerns if the user opens different tabs and tries to create models in new tabs. ------------------------------ In src/state/modelStore.ts <#138 (comment)> : > @@ -0,0 +1,74 @@ +import { create } from 'zustand' +import { devtools, persist } from 'zustand/middleware' +import { upsert_user } from ***@***.***/explore/upsert_user' +import { Model, TrainingRequest } from ***@***.***/client' + +type IModel = Omit<Omit<Model, 'createdAt'>, 'updatedAt'> +type ITrainRequest = Omit<Omit<TrainingRequest, 'createdAt'>, 'updatedAt'> + +type Store = { + model: IModel | null but that's alright, we can restrict user-usage to just one-tab I guess? — Reply to this email directly, view it on GitHub <#138 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHKFVMLGRF2CFW4OT4RFTMTYD7RFXAVCNFSM6AAAAAA7HFGUT2VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTOMRWGEZDINJQGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>