zulip/static/js/message_store.js

219 lines
6.5 KiB
JavaScript
Raw Normal View History

const stored_messages = {};
/*
We keep a set of user_ids for all people
who have sent stream messages or who have
been on PMs sent by the user.
We will use this in search to prevent really
large result sets for realms that have lots
of users who haven't sent messages recently.
We'll likely eventually want to replace this with
accessing some combination of data from recent_senders
and pm_conversations for better accuracy.
*/
const message_user_ids = new Set();
exports.user_ids = function () {
return Array.from(message_user_ids);
};
exports.get = function get(message_id) {
return stored_messages[message_id];
};
exports.each = function (f) {
_.each(stored_messages, function (message) {
f(message);
});
};
exports.get_pm_emails = function (message) {
function email(user_id) {
const person = people.get_person_from_user_id(user_id);
if (!person) {
blueslip.error('Unknown user id ' + user_id);
return '?';
}
return person.email;
}
const user_ids = people.pm_with_user_ids(message);
const emails = _.map(user_ids, email).sort();
return emails.join(', ');
};
exports.get_pm_full_names = function (message) {
function name(user_id) {
const person = people.get_person_from_user_id(user_id);
if (!person) {
blueslip.error('Unknown user id ' + user_id);
return '?';
}
return person.full_name;
}
const user_ids = people.pm_with_user_ids(message);
const names = _.map(user_ids, name).sort();
return names.join(', ');
};
exports.process_message_for_recent_private_messages = function (message) {
const user_ids = people.pm_with_user_ids(message);
if (!user_ids) {
return;
}
_.each(user_ids, function (user_id) {
pm_conversations.set_partner(user_id);
});
pm_conversations.recent.insert(user_ids, message.id);
};
exports.set_message_booleans = function (message) {
const flags = message.flags || [];
function convert_flag(flag_name) {
return flags.indexOf(flag_name) >= 0;
}
message.unread = !convert_flag('read');
message.historical = convert_flag('historical');
message.starred = convert_flag('starred');
message.mentioned = convert_flag('mentioned') || convert_flag('wildcard_mentioned');
message.mentioned_me_directly = convert_flag('mentioned');
message.collapsed = convert_flag('collapsed');
message.alerted = convert_flag('has_alert_word');
// Once we have set boolean flags here, the `flags` attribute is
// just a distraction, so we delete it. (All the downstream code
// uses booleans.)
delete message.flags;
};
exports.init_booleans = function (message) {
// This initializes booleans for the local-echo path where
// we don't have flags from the server yet. (We want to
// explicitly set flags to false to be consistent with other
// codepaths.)
message.unread = false;
message.historical = false;
message.starred = false;
message.mentioned = false;
message.mentioned_me_directly = false;
message.collapsed = false;
message.alerted = false;
};
exports.update_booleans = function (message, flags) {
// When we get server flags for local echo or message edits,
// we are vulnerable to race conditions, so only update flags
// that are driven by message content.
function convert_flag(flag_name) {
return flags.indexOf(flag_name) >= 0;
}
message.mentioned = convert_flag('mentioned') || convert_flag('wildcard_mentioned');
message.mentioned_me_directly = convert_flag('mentioned');
message.alerted = convert_flag('has_alert_word');
};
2017-03-19 18:19:48 +01:00
exports.add_message_metadata = function (message) {
const cached_msg = stored_messages[message.id];
if (cached_msg !== undefined) {
// Copy the match topic and content over if they exist on
// the new message
if (util.get_match_topic(message) !== undefined) {
util.set_match_data(cached_msg, message);
}
return cached_msg;
}
message.sent_by_me = people.is_current_user(message.sender_email);
people.extract_people_from_message(message);
people.maybe_incr_recipient_count(message);
const sender = people.get_person_from_user_id(message.sender_id);
if (sender) {
message.sender_full_name = sender.full_name;
message.sender_email = sender.email;
}
// Convert topic even for PMs, as legacy code
// wants the empty field.
util.convert_message_topic(message);
switch (message.type) {
case 'stream':
message.is_stream = true;
message.stream = message.display_recipient;
message.reply_to = message.sender_email;
topic_data.add_message({
stream_id: message.stream_id,
topic_name: util.get_message_topic(message),
message_id: message.id,
});
recent_senders.process_message_for_senders(message);
message_user_ids.add(message.sender_id);
break;
case 'private':
message.is_private = true;
message.reply_to = util.normalize_recipients(
exports.get_pm_emails(message));
message.display_reply_to = exports.get_pm_full_names(message);
message.pm_with_url = people.pm_with_url(message);
message.to_user_ids = people.pm_reply_user_string(message);
exports.process_message_for_recent_private_messages(message);
if (people.is_my_user_id(message.sender_id)) {
_.each(message.display_recipient, (recip) => {
message_user_ids.add(recip.id);
});
}
break;
}
alert_words.process_message(message);
Add frontend support for emoji reactions. This commit replaces the placeholder "clipboard" button with a reaction button. This is done on any message that can't be edited. Also, on messages sent by the user the actions popover (toggled by the down chevron icon) contains an option to add a reaction. When clicked, a popover with a search bar and a list of emojis is displayed. If the right sidebar is collapsed (the viewport is small), the popover is placed to the left of the button. Focus is set to the search bar. Typing in the search bar filters emojis. Emojis with which the user has reacted to this message are highlighted. Clicking them sends an API request to remove that reaction. Clicking on non-highlighted emojis sends an API request to add a reaction. When the popover loses focus it is closed. The frontend listens for reaction events. When an add-reaction event is received, the emoji is displayed at the bottom of the message with a count initialized to 1. If there was an existing reaction to the message with the same emoji, the count is incremented. Old messages fetched from the server contain reactions. They are displayed (along with title and count) at the bottom of each message. When clicking the emoji reaction at the bottom of the message, if the user has already reacted with that emoji to this message, the reaction is removed and the count is decremented. Otherwise, a reaction is added and the count is incremented. Hovering over the emoji reaction at the bottom of the message displays a list of users who have reacted with this emoji along with the emoji name. Hovering over the emoji reactions at the bottom of the message displays a button to add a reaction. Fixes #541.
2016-12-02 13:23:23 +01:00
if (!message.reactions) {
message.reactions = [];
}
stored_messages[message.id] = message;
return message;
2017-03-19 18:19:48 +01:00
};
exports.reify_message_id = function (opts) {
const old_id = opts.old_id;
const new_id = opts.new_id;
if (pointer.furthest_read === old_id) {
pointer.set_furthest_read(new_id);
}
if (stored_messages[old_id]) {
stored_messages[new_id] = stored_messages[old_id];
delete stored_messages[old_id];
}
_.each([message_list.all, home_msg_list, message_list.narrowed], function (msg_list) {
if (msg_list !== undefined) {
msg_list.change_message_id(old_id, new_id);
if (msg_list.view !== undefined) {
msg_list.view.change_message_id(old_id, new_id);
}
}
});
};
window.message_store = exports;