Add error messaging for creating entities with properties that do not exist
Aidan O'Connor
As a Port admin, I occasionally add entities to Port using the API. Sometimes, I try to add a property that does not (yet) exist, or I misspell a property identifier. Currently, the API allows for the entity to be created, and instead of raising an error about an incorrectly entered or nonexistent property, the entity is allowed to be created and properties which did not receive value specifications from the API call are assigned the default property. This is not ideal: I would like either to have an error raised blocking the entity, or (ideally) have an error raised explaining that I tried to add a value to a property that does not exist.