Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • 2
    Does your requirements matrix, design document or software specifications state the need for an additional endpoint to support questions directly? If not, YAGNI. Build it when you can actually demonstrate a need for it. Commented Aug 24, 2017 at 16:35
  • @RobertHarvey It's not a requirement, but it's simple to add additional endpoints in the current implementation. I think the only need for it currently would be to simplify endpoints and make them slightly more intuitive. Commented Aug 24, 2017 at 16:44
  • How I would interpret the "/api/exams/{id}/questions/{id}" would be the questions for that specific exam. I would see "/api/question/{id}" as getting it out of a pool of all the questions. It may be the same result, but the interpretation is different. From the one you are limiting yourself to an exam, the other you are picking it from all the questions. Commented Aug 25, 2017 at 12:50
  • Take a look here. Commented Aug 27, 2017 at 19:09