New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Map out API routes for workspaces - #173
Comments
Front end, please add on to this if necessary! |
For rendering workspaces here is some of the information that would need to be passed back -> front for each individual workspace:
We might want to talk about what exactly we want security looks like - what does it means when a user successfully joins a workspace? |
For rendering individual workspaces, here is what is needed for each article:
Just in general for frontend people, there is a set up for how this could be done on lines 118-135 in Results.jsx |
The skeleton fetch requests in place right now (please feel free to add to this!) Workspaces.jsx:
Right now I have it passing in the user name of the current user in the header.
Right now: I have it passing in the workspace name and password. 3.executeCreate: Responsible for sending information about a workspace someone is trying to create. Guaranteed through validation to always have a name and password set by the user. Right now: I have it passing in the workspace name and password. indvidualWorkspacePage.jsx: Responsible for getting the information about each articles in an individual workspace. Right now I have it sending the workspace name and the user name (?) in the header. Results.jsx:
Workspaces.jsx:
|
I don't think count is needed, so either way is fine. |
The text was updated successfully, but these errors were encountered: