integrate api workspaces

[sanglevinh]

No description provided.

[itutu-tienday]

I have noted the points raised. Please confirm.

[itutu-tienday]

@sanglevinh
The following error seems to be occurring on the API side when displaying the Workspaces screen on the latest branch as of now.

File "/workspace/optinist-for-server/studio/app/common/routers/workspace.py", line 58, in search_workspaces
    ws.__dict__["user"] = db.query(common_model.User).get(ws.user_id)
AttributeError: 'Workspace' object has no attribute 'user_id'

It seems that the above user_id is being removed on the API side in commit 0bec77a, but is the above error occurring in your environment?

[sanglevinh]

@sanglevinh The following error seems to be occurring on the API side when displaying the Workspaces screen on the latest branch as of now.

File "/workspace/optinist-for-server/studio/app/common/routers/workspace.py", line 58, in search_workspaces
    ws.__dict__["user"] = db.query(common_model.User).get(ws.user_id)
AttributeError: 'Workspace' object has no attribute 'user_id'

It seems that the above user_id is being removed on the API side in commit 0bec77a, but is the above error occurring in your environment?

@itutu-tienday

I reverted it
I think it should be fixed in the backend later.

Is this attribute required as API schema?

[ReiHashimoto]

@quanpython
Could you refactor the models?
(In other PR can be OK)

It seems relationship and FK is not defined in current models.

FYI
https://docs.sqlalchemy.org/en/20/orm/basic_relationships.html#one-to-many

I don't think we have to insert User object into Workspace object like this process.

With relation, we can get User Object from user attribute.

[ReiHashimoto]

Backend requires refactor( as this comment), but frontend looks fine.