-
Notifications
You must be signed in to change notification settings - Fork 31
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
Backend Architecture #10
Comments
Possible use of Mongoose and Mongo |
I'd like to work on the backend architecture, particularly the answer model, but the question model might need to come first. It would probably be best to link each answer to a specific question by referencing the question id in the answer model. |
I'd like to work on this as well. I think it would be a good idea to have the backend boilerplate set up first, directories, basic server, Can I take up this issue? |
That does sound good! I don't see anyone else talking about it, so you should be good to go ahead and start. |
I was holding off because I did see someone working on it in the channel. @NickSramcik is this being worked on? |
Just submitted a PR that has basic MVC functionality for the backend. This is a VERY ROUGH DRAFT and will need more input to be what we want it to be. |
I'm going to get to work on some models now. |
* Create PostModels.js Assumes the database will store questions and their answers, and allow comments. Contains comments with minimal explanations and reference links. * Rename PostModels.js to postModels.js Title capitalization change. * Update postModels.js Add comments, fix minor errors * Update userModel.js Remove Question. * Update postModels.js Change upvotes and downvotes to arrays of references to users.
We need to begin constructing our backend so that we can handle more flexibility with our questions and answers.
Specifically, we need:
The text was updated successfully, but these errors were encountered: