Open dmlary opened 4 years ago
Alright, implementing this as PUT /component/<id>/<field>
, and updating each field directly. This closely mirrors the behavior we experience in pry, and removes the difficulty of sorting out which fields were modified if we were to send all the values at once.
End UI will be editing a single field at a time. When save is hit, it propagates to the server.
We will need to open an issue for component generation counting to prevent web-interface from stomping on a component value that changed underneath them.
Created ComponentFieldInput to handle all of this "magically"
For an existing component on an entity: