2. New issues

Compared to the single-class app discussed in Part 2 (Validation Tutorial), we have to deal with a number of new technical issues:

  1. In the controller code we now have to take care of reference properties that require

    • validation of referential integrity constraints (ID references).

    • conversion between (internal) object references and (external) ID references in the serialization and de-serialization procedures.

  2. In the user interface ("view") code we now have to take care of

    • showing information about associated objects in the list objects use case;

    • allowing to select an associated object from a list of all existing instances of the target class in the create object and update object use cases.

Based on the Parse REST API, Pointer is just like a foreign key and it would be very efficient for handling the Many-to-One Relation.

The last issue, allowing to select an associated object from a list of all existing instances of some class, can be solved with the help of an HTML select form element with an Angular directive ngOptions as an attribute. What should be also noticed is, that with the improvement of our project, the code will become increasingly large. We will restructure the folder, which will be discussed in following section.