At most cases, Database Schematic Objects (Models) are PersistedModels, that could be CREATED, READ, UPDATED and DESTROYED. Yet at other cases, we need Immutable objects, that could only be CREAETD or DESTROYED, to help us come up with simplistic system designs.
I would propose here, to add a base class called ImmutablePersistedModel, to bring such a functionality to Loopback/Neaty.
R = @yorkie
At most cases, Database Schematic Objects (Models) are
PersistedModels, that could be CREATED, READ, UPDATED and DESTROYED. Yet at other cases, we need Immutable objects, that could only be CREAETD or DESTROYED, to help us come up with simplistic system designs.I would propose here, to add a base class called
ImmutablePersistedModel, to bring such a functionality to Loopback/Neaty.R = @yorkie