Update Question Service #6
Conversation
.idea/.gitignore
Outdated
There was a problem hiding this comment.
Think the JetBrains .idea folder can be excluded with .gitignore?
There was a problem hiding this comment.
Okay, I will exclude it out.
|
|
||
| ### Parameters: | ||
|
|
||
| - `limit` - The number of questions to be returned (Required) |
There was a problem hiding this comment.
Doesn't this endpoint retrieve a single question?
There was a problem hiding this comment.
Oh the description I wrote was a bit misleading. I was thinking we could just have set it by default to 1 for finding a question for a user. Then for values other than 1, I was thinking we could have it just in case there's some other usage for it (eg; retrieval of questions that matches the param for admin to look through). But I guess the randomised nature of this wouldn't really work that well for the example I gave LOL unless there's another boolean flag to indicate if we want random or not.
There was a problem hiding this comment.
yep sounds good, we could have optional parameters topics, difficulty, limit and offset in the get all questions endpoint for table pagination and filtering 😄
| ### Parameters: | ||
|
|
||
| - `limit` - The number of questions to be returned (Required) | ||
| - `topics` - The topic of the question (Required) |
There was a problem hiding this comment.
Should we allow users to submit multiple topics that they are interested in?
There was a problem hiding this comment.
Yeah agreed. This probably will improve user experience in matching too since the user would have a wider range of topics.
|
|
||
| - `limit` - The number of questions to be returned (Required) | ||
| - `topics` - The topic of the question (Required) | ||
| - `languages` - The language of the question (Required) |
There was a problem hiding this comment.
Does this mean that we are going to customize the code template for each question? Personally, I'm not too keen on doing so, and hence I don't think we need this field.
McNaBry
added
documentation
- questionController.ts: Implemented new get endpoint for retrieving questions. - questionModel.ts: Updated `Difficulty` enum to `Hard` enum. - questionRoutes.ts: Added new routes for handling get requests. - helper.ts: Added helper function for improved error handling.
KhoonSun47
changed the title
Update README