To understand the motivation here, imagine a UI where a marketplace is built by dragging and dropping OC resources and connecting them up visually in a diagram. Maybe assignments are arrows. This library could help support such a tool by providing insight into what diagrams are valid or invalid. But it would have to provide very specific, useful info on where any problems lie.
Currently an error is simply a string. It needs to be a strongly-typed object.
It should include all information about where the error can be found - resource type, resource ID, parent resource ID, property. (What to do if no ID?)
It should include an error type from an enum of options - foreign key, required field, data type, ect.
It should include any relevant data about other fields that influence this error. For example, the securityprofile.userID field can be valid or invalid depending on the securityprofile.buyerID field.
A message string field is probably still needed. But the ideal goal would be to be able to generate the message based on the data in the error
To understand the motivation here, imagine a UI where a marketplace is built by dragging and dropping OC resources and connecting them up visually in a diagram. Maybe assignments are arrows. This library could help support such a tool by providing insight into what diagrams are valid or invalid. But it would have to provide very specific, useful info on where any problems lie.
Currently an error is simply a string. It needs to be a strongly-typed object.