This is a result of how the frontend consumes data. We should file a follow-up bug on this!