If for some reason an update did not go through (for example, concurrently updating the same topic twice), we were logging something like: ``` create_errors_json called with unrecognized type: #<Topic ``` This happened because we knew an error occurred but the active record object had no errors attached. This patch fixes the issue by attaching a proper error message in the event that this happens. |
||
|---|---|---|
| .. | ||
| assets | ||
| controllers | ||
| helpers | ||
| jobs | ||
| mailers | ||
| models | ||
| serializers | ||
| services | ||
| views | ||