The client already has all the information about the current user so there is no need for us to be serializing the current `User` object each time per channel that is preloaded. In production, profiling shows that this unneeded serializing adds a roughly 5% overhead to a request. |
||
|---|---|---|
| .. | ||
| admin_chat_index_serializer.rb | ||
| base_chat_channel_membership_serializer.rb | ||
| chat_channel_index_serializer.rb | ||
| chat_channel_search_serializer.rb | ||
| chat_channel_serializer.rb | ||
| chat_in_reply_to_serializer.rb | ||
| chat_message_serializer.rb | ||
| chat_view_serializer.rb | ||
| chat_webhook_event_serializer.rb | ||
| direct_message_serializer.rb | ||
| incoming_chat_webhook_serializer.rb | ||
| reviewable_chat_message_serializer.rb | ||
| structured_channel_serializer.rb | ||
| user_chat_channel_membership_serializer.rb | ||
| user_chat_message_bookmark_serializer.rb | ||
| user_with_custom_fields_and_status_serializer.rb | ||