We are making a quiz application, I'm trying to integrate my Angular 2 UI with the REST api.Our Quiz domain model consist of the following (simplified) hierarchy:-Quiz-Category-Question-Choicewhere parent doesn't know its children, but child knows its parent. For example, Choice has a reference for a Question, but Question doesn't have reference to choice. We chose this approach to be able to fetch the quiz data more flexible and modular approach, also avoiding circular references.However, in the front end it's counter-intuitive to use inverted linking, as views are built naturally layer-by-layer iterating deeper in the domain object structure. It makes sense to render view for Question first, and render sub-view for Choices after. It just seems impossible with the current domain model, where I should start from Choice.My question is, if it's common or approved to convert the domain model on the front end, so I wold gather all data and add Choice reference to Question afterwards, making the model compatible for top-down approach? And of course convert it back when POSTing to REST api.Does this indicate bad design, or is it approved to alter the domain model?
Is it anti-pattern to alter domain model on front end?
design;design patterns;object oriented;architecture;rest