mirror of
https://github.com/zulip/zulip.git
synced 2025-10-31 20:13:46 +00:00
1f156230b0
We add these two functions to the API,
so that we no longer have `alert_words_ui`
using private data from `alert_word`:
alert_words.has_alert_word()
alert_words.get_word_list()
And to initialize the data, we have a proper
`initialize` method that is passed in only
the parameters that it needs from `ui_init`.
(We also move the step of deleting `alert_words`
from `page_params` to the `ui_init` module.)
Because it's a bit less cumbersome to initialize
`alert_words`, we now just it directly in the
node tests for `alert_words_ui`.
76 lines
2.9 KiB
JavaScript
76 lines
2.9 KiB
JavaScript
// For simplicity, we use a list for our internal
|
|
// data, since that matches what the server sends us.
|
|
let my_alert_words = [];
|
|
|
|
exports.set_words = function (words) {
|
|
my_alert_words = words;
|
|
};
|
|
|
|
exports.get_word_list = function () {
|
|
// People usually only have a couple alert
|
|
// words, so it's cheap to be defensive
|
|
// here and give a copy of the list to
|
|
// our caller (in case they want to sort it
|
|
// or something).
|
|
return [...my_alert_words];
|
|
};
|
|
|
|
exports.has_alert_word = function (word) {
|
|
return my_alert_words.includes(word);
|
|
};
|
|
|
|
// escape_user_regex taken from jquery-ui/autocomplete.js,
|
|
// licensed under MIT license.
|
|
function escape_user_regex(value) {
|
|
return value.replace(/[\-\[\]{}()*+?.,\\\^$|#\s]/g, "\\$&");
|
|
}
|
|
|
|
exports.process_message = function (message) {
|
|
// Parsing for alert words is expensive, so we rely on the host
|
|
// to tell us there any alert words to even look for.
|
|
if (!message.alerted) {
|
|
return;
|
|
}
|
|
|
|
for (const word of my_alert_words) {
|
|
const clean = escape_user_regex(word);
|
|
const before_punctuation = '\\s|^|>|[\\(\\".,\';\\[]';
|
|
const after_punctuation = '\\s|$|<|[\\)\\"\\?!:.,\';\\]!]';
|
|
|
|
|
|
const regex = new RegExp('(' + before_punctuation + ')' +
|
|
'(' + clean + ')' +
|
|
'(' + after_punctuation + ')', 'ig');
|
|
message.content = message.content.replace(regex, function (match, before, word,
|
|
after, offset, content) {
|
|
// Logic for ensuring that we don't muck up rendered HTML.
|
|
const pre_match = content.substring(0, offset);
|
|
// We want to find the position of the `<` and `>` only in the
|
|
// match and the string before it. So, don't include the last
|
|
// character of match in `check_string`. This covers the corner
|
|
// case when there is an alert word just before `<` or `>`.
|
|
const check_string = pre_match + match.substring(0, match.length - 1);
|
|
const in_tag = check_string.lastIndexOf('<') > check_string.lastIndexOf('>');
|
|
// Matched word is inside a HTML tag so don't perform any highlighting.
|
|
if (in_tag === true) {
|
|
return before + word + after;
|
|
}
|
|
return before + "<span class='alert-word'>" + word + "</span>" + after;
|
|
});
|
|
}
|
|
};
|
|
|
|
exports.notifies = function (message) {
|
|
// We exclude ourselves from notifications when we type one of our own
|
|
// alert words into a message, just because that can be annoying for
|
|
// certain types of workflows where everybody on your team, including
|
|
// yourself, sets up an alert word to effectively mention the team.
|
|
return !people.is_current_user(message.sender_email) && message.alerted;
|
|
};
|
|
|
|
exports.initialize = (params) => {
|
|
my_alert_words = params.alert_words;
|
|
};
|
|
|
|
window.alert_words = exports;
|