You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The V4 UpdateEntity endpoint expects to be explicitly given the entity type in the body of the request, even though this is not a property that can actually be updated with this endpoint. mix.cli users are currently forced to provide the entity-type which does not provide the best of experiences.
A solution is have mix-cli query the GetEntity endpoint first to retrieve the entity type and proceed with it for the call to the UpdateEntity endpoint.
But providing this also brings up more error scenarios to consider. For instance, we cannot let users change the type of a base entity and it would be nice to capture this and warn users about it. In the current implementation, "base" is not a possible values for the --entity-type flag so we don't have this issue. All this to say that this is not only about grabbing the entity type from the GetEntity endpoint, we also need to think about the differnt paths the interaction can take after.
The text was updated successfully, but these errors were encountered:
The V4 UpdateEntity endpoint expects to be explicitly given the entity type in the body of the request, even though this is not a property that can actually be updated with this endpoint. mix.cli users are currently forced to provide the entity-type which does not provide the best of experiences.
A solution is have mix-cli query the GetEntity endpoint first to retrieve the entity type and proceed with it for the call to the UpdateEntity endpoint.
But providing this also brings up more error scenarios to consider. For instance, we cannot let users change the type of a base entity and it would be nice to capture this and warn users about it. In the current implementation, "base" is not a possible values for the --entity-type flag so we don't have this issue. All this to say that this is not only about grabbing the entity type from the GetEntity endpoint, we also need to think about the differnt paths the interaction can take after.
The text was updated successfully, but these errors were encountered: