2022-11-02 09:41:30 -04:00
|
|
|
|
import I18n from "I18n";
|
|
|
|
|
import { performEmojiUnescape } from "pretty-text/emoji";
|
|
|
|
|
|
|
|
|
|
let customMarkdownCookFn;
|
|
|
|
|
|
|
|
|
|
const chatTranscriptRule = {
|
|
|
|
|
tag: "chat",
|
|
|
|
|
|
|
|
|
|
replace: function (state, tagInfo, content) {
|
|
|
|
|
// shouldn't really happen but we don't want to break rendering if it does
|
|
|
|
|
if (!customMarkdownCookFn) {
|
|
|
|
|
return;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
const options = state.md.options.discourse;
|
|
|
|
|
const [username, messageIdStart, messageTimeStart] =
|
|
|
|
|
(tagInfo.attrs.quote && tagInfo.attrs.quote.split(";")) || [];
|
|
|
|
|
const reactions = tagInfo.attrs.reactions;
|
|
|
|
|
const multiQuote = !!tagInfo.attrs.multiQuote;
|
|
|
|
|
const noLink = !!tagInfo.attrs.noLink;
|
|
|
|
|
const channelName = tagInfo.attrs.channel;
|
|
|
|
|
const channelId = tagInfo.attrs.channelId;
|
|
|
|
|
const channelLink = channelId
|
|
|
|
|
? options.getURL(`/chat/channel/${channelId}/-`)
|
|
|
|
|
: null;
|
|
|
|
|
|
|
|
|
|
if (!username || !messageIdStart || !messageTimeStart) {
|
|
|
|
|
return;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
let wrapperDivToken = state.push("div_chat_transcript_wrap", "div", 1);
|
|
|
|
|
let wrapperClasses = ["chat-transcript"];
|
|
|
|
|
|
|
|
|
|
if (!!tagInfo.attrs.chained) {
|
|
|
|
|
wrapperClasses.push("chat-transcript-chained");
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
wrapperDivToken.attrs = [["class", wrapperClasses.join(" ")]];
|
|
|
|
|
wrapperDivToken.attrs.push(["data-message-id", messageIdStart]);
|
|
|
|
|
wrapperDivToken.attrs.push(["data-username", username]);
|
|
|
|
|
wrapperDivToken.attrs.push(["data-datetime", messageTimeStart]);
|
|
|
|
|
|
|
|
|
|
if (reactions) {
|
|
|
|
|
wrapperDivToken.attrs.push(["data-reactions", reactions]);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
if (channelName) {
|
|
|
|
|
wrapperDivToken.attrs.push(["data-channel-name", channelName]);
|
|
|
|
|
|
|
|
|
|
if (multiQuote) {
|
|
|
|
|
let metaDivToken = state.push("div_chat_transcript_meta", "div", 1);
|
|
|
|
|
metaDivToken.attrs = [["class", "chat-transcript-meta"]];
|
|
|
|
|
const channelToken = state.push("html_inline", "", 0);
|
|
|
|
|
channelToken.content = I18n.t("chat.quote.original_channel", {
|
|
|
|
|
channel: channelName,
|
|
|
|
|
channelLink,
|
|
|
|
|
});
|
|
|
|
|
state.push("div_chat_transcript_meta", "div", -1);
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
if (channelId) {
|
|
|
|
|
wrapperDivToken.attrs.push(["data-channel-id", channelId]);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
let userDivToken = state.push("div_chat_transcript_user", "div", 1);
|
|
|
|
|
userDivToken.attrs = [["class", "chat-transcript-user"]];
|
|
|
|
|
|
|
|
|
|
// start: user avatar
|
|
|
|
|
let avatarDivToken = state.push(
|
|
|
|
|
"div_chat_transcript_user_avatar",
|
|
|
|
|
"div",
|
|
|
|
|
1
|
|
|
|
|
);
|
|
|
|
|
avatarDivToken.attrs = [["class", "chat-transcript-user-avatar"]];
|
|
|
|
|
|
|
|
|
|
// server-side, we need to lookup the avatar from the username
|
|
|
|
|
let avatarImg;
|
|
|
|
|
if (options.lookupAvatar) {
|
|
|
|
|
avatarImg = options.lookupAvatar(username);
|
|
|
|
|
}
|
|
|
|
|
if (avatarImg) {
|
|
|
|
|
const avatarImgToken = state.push("html_inline", "", 0);
|
|
|
|
|
avatarImgToken.content = avatarImg;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
state.push("div_chat_transcript_user_avatar", "div", -1);
|
|
|
|
|
// end: user avatar
|
|
|
|
|
|
|
|
|
|
// start: username
|
|
|
|
|
let usernameDivToken = state.push("div_chat_transcript_username", "div", 1);
|
|
|
|
|
usernameDivToken.attrs = [["class", "chat-transcript-username"]];
|
|
|
|
|
|
|
|
|
|
let displayName;
|
|
|
|
|
if (options.formatUsername) {
|
|
|
|
|
displayName = options.formatUsername(username);
|
|
|
|
|
} else {
|
|
|
|
|
displayName = username;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
const usernameToken = state.push("html_inline", "", 0);
|
|
|
|
|
usernameToken.content = displayName;
|
|
|
|
|
|
|
|
|
|
state.push("div_chat_transcript_username", "div", -1);
|
|
|
|
|
// end: username
|
|
|
|
|
|
|
|
|
|
// start: time + link to message
|
|
|
|
|
let datetimeDivToken = state.push("div_chat_transcript_datetime", "div", 1);
|
|
|
|
|
datetimeDivToken.attrs = [["class", "chat-transcript-datetime"]];
|
|
|
|
|
|
|
|
|
|
// for some cases, like archiving, we don't want the link to the
|
|
|
|
|
// chat message because it will just result in a 404
|
|
|
|
|
// also handles the case where the quote doesn’t contain
|
|
|
|
|
// enough data to build a valid channel/message link
|
|
|
|
|
if (noLink || !channelLink) {
|
|
|
|
|
let spanToken = state.push("span_open", "span", 1);
|
|
|
|
|
spanToken.attrs = [["title", messageTimeStart]];
|
|
|
|
|
|
|
|
|
|
spanToken.block = false;
|
|
|
|
|
spanToken = state.push("span_close", "span", -1);
|
|
|
|
|
spanToken.block = false;
|
|
|
|
|
} else {
|
|
|
|
|
let linkToken = state.push("link_open", "a", 1);
|
|
|
|
|
linkToken.attrs = [
|
|
|
|
|
["href", `${channelLink}?messageId=${messageIdStart}`],
|
|
|
|
|
["title", messageTimeStart],
|
|
|
|
|
];
|
|
|
|
|
|
|
|
|
|
linkToken.block = false;
|
|
|
|
|
linkToken = state.push("link_close", "a", -1);
|
|
|
|
|
linkToken.block = false;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
state.push("div_chat_transcript_datetime", "div", -1);
|
|
|
|
|
// end: time + link to message
|
|
|
|
|
|
|
|
|
|
// start: channel link for !multiQuote
|
|
|
|
|
if (channelName && !multiQuote) {
|
|
|
|
|
let channelLinkToken = state.push("link_open", "a", 1);
|
|
|
|
|
channelLinkToken.attrs = [
|
|
|
|
|
["class", "chat-transcript-channel"],
|
|
|
|
|
["href", channelLink],
|
|
|
|
|
];
|
|
|
|
|
let inlineTextToken = state.push("html_inline", "", 0);
|
|
|
|
|
inlineTextToken.content = `#${channelName}`;
|
|
|
|
|
channelLinkToken = state.push("link_close", "a", -1);
|
|
|
|
|
channelLinkToken.block = false;
|
|
|
|
|
}
|
|
|
|
|
// end: channel link for !multiQuote
|
|
|
|
|
|
|
|
|
|
state.push("div_chat_transcript_user", "div", -1);
|
|
|
|
|
|
|
|
|
|
let messagesToken = state.push("div_chat_transcript_messages", "div", 1);
|
|
|
|
|
messagesToken.attrs = [["class", "chat-transcript-messages"]];
|
|
|
|
|
|
|
|
|
|
// rendering chat message content with limited markdown rule subset
|
|
|
|
|
const token = state.push("html_raw", "", 1);
|
FEATURE: Generic hashtag autocomplete lookup and markdown cooking (#18937)
This commit fleshes out and adds functionality for the new `#hashtag` search and
lookup system, still hidden behind the `enable_experimental_hashtag_autocomplete`
feature flag.
**Serverside**
We have two plugin API registration methods that are used to define data sources
(`register_hashtag_data_source`) and hashtag result type priorities depending on
the context (`register_hashtag_type_in_context`). Reading the comments in plugin.rb
should make it clear what these are doing. Reading the `HashtagAutocompleteService`
in full will likely help a lot as well.
Each data source is responsible for providing its own **lookup** and **search**
method that returns hashtag results based on the arguments provided. For example,
the category hashtag data source has to take into account parent categories and
how they relate, and each data source has to define their own icon to use for the
hashtag, and so on.
The `Site` serializer has two new attributes that source data from `HashtagAutocompleteService`.
There is `hashtag_icons` that is just a simple array of all the different icons that
can be used for allowlisting in our markdown pipeline, and there is `hashtag_context_configurations`
that is used to store the type priority orders for each registered context.
When sending emails, we cannot render the SVG icons for hashtags, so
we need to change the HTML hashtags to the normal `#hashtag` text.
**Markdown**
The `hashtag-autocomplete.js` file is where I have added the new `hashtag-autocomplete`
markdown rule, and like all of our rules this is used to cook the raw text on both the clientside
and on the serverside using MiniRacer. Only on the server side do we actually reach out to
the database with the `hashtagLookup` function, on the clientside we just render a plainer
version of the hashtag HTML. Only in the composer preview do we do further lookups based
on this.
This rule is the first one (that I can find) that uses the `currentUser` based on a passed
in `user_id` for guardian checks in markdown rendering code. This is the `last_editor_id`
for both the post and chat message. In some cases we need to cook without a user present,
so the `Discourse.system_user` is used in this case.
**Chat Channels**
This also contains the changes required for chat so that chat channels can be used
as a data source for hashtag searches and lookups. This data source will only be
used when `enable_experimental_hashtag_autocomplete` is `true`, so we don't have
to worry about channel results suddenly turning up.
------
**Known Rough Edges**
- Onebox excerpts will not render the icon svg/use tags, I plan to address that in a follow up PR
- Selecting a hashtag + pressing the Quote button will result in weird behaviour, I plan to address that in a follow up PR
- Mixed hashtag contexts for hashtags without a type suffix will not work correctly, e.g. #ux which is both a category and a channel slug will resolve to a category when used inside a post or within a [chat] transcript in that post. Users can get around this manually by adding the correct suffix, for example ::channel. We may get to this at some point in future
- Icons will not show for the hashtags in emails since SVG support is so terrible in email (this is not likely to be resolved, but still noting for posterity)
- Additional refinements and review fixes wil
2022-11-20 17:37:06 -05:00
|
|
|
|
|
2022-11-02 09:41:30 -04:00
|
|
|
|
token.content = customMarkdownCookFn(content);
|
|
|
|
|
state.push("html_raw", "", -1);
|
|
|
|
|
|
|
|
|
|
if (reactions) {
|
|
|
|
|
let emojiHtmlCache = {};
|
|
|
|
|
let reactionsToken = state.push(
|
|
|
|
|
"div_chat_transcript_reactions",
|
|
|
|
|
"div",
|
|
|
|
|
1
|
|
|
|
|
);
|
|
|
|
|
reactionsToken.attrs = [["class", "chat-transcript-reactions"]];
|
|
|
|
|
|
|
|
|
|
reactions.split(";").forEach((reaction) => {
|
|
|
|
|
const split = reaction.split(":");
|
|
|
|
|
const emoji = split[0];
|
|
|
|
|
const usernames = split[1].split(",");
|
|
|
|
|
|
|
|
|
|
const reactToken = state.push("div_chat_transcript_reaction", "div", 1);
|
|
|
|
|
reactToken.attrs = [["class", "chat-transcript-reaction"]];
|
|
|
|
|
const emojiToken = state.push("html_inline", "", 0);
|
|
|
|
|
if (!emojiHtmlCache[emoji]) {
|
|
|
|
|
emojiHtmlCache[emoji] = performEmojiUnescape(`:${emoji}:`, {
|
|
|
|
|
getURL: options.getURL,
|
|
|
|
|
emojiSet: options.emojiSet,
|
|
|
|
|
emojiCDNUrl: options.emojiCDNUrl,
|
|
|
|
|
enableEmojiShortcuts: options.enableEmojiShortcuts,
|
|
|
|
|
inlineEmoji: options.inlineEmoji,
|
|
|
|
|
lazy: true,
|
|
|
|
|
});
|
|
|
|
|
}
|
|
|
|
|
emojiToken.content = `${
|
|
|
|
|
emojiHtmlCache[emoji]
|
|
|
|
|
} ${usernames.length.toString()}`;
|
|
|
|
|
state.push("div_chat_transcript_reaction", "div", -1);
|
|
|
|
|
});
|
|
|
|
|
state.push("div_chat_transcript_reactions", "div", -1);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
state.push("div_chat_transcript_messages", "div", -1);
|
|
|
|
|
state.push("div_chat_transcript_wrap", "div", -1);
|
|
|
|
|
return true;
|
|
|
|
|
},
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
export function setup(helper) {
|
|
|
|
|
helper.allowList([
|
|
|
|
|
"div[class=chat-transcript]",
|
|
|
|
|
"div[class=chat-transcript chat-transcript-chained]",
|
|
|
|
|
"div.chat-transcript-meta",
|
|
|
|
|
"div.chat-transcript-user",
|
|
|
|
|
"div.chat-transcript-username",
|
|
|
|
|
"div.chat-transcript-user-avatar",
|
|
|
|
|
"div.chat-transcript-messages",
|
|
|
|
|
"div.chat-transcript-datetime",
|
|
|
|
|
"div.chat-transcript-reactions",
|
|
|
|
|
"div.chat-transcript-reaction",
|
|
|
|
|
"span[title]",
|
|
|
|
|
"div[data-message-id]",
|
|
|
|
|
"div[data-channel-name]",
|
|
|
|
|
"div[data-channel-id]",
|
|
|
|
|
"div[data-username]",
|
|
|
|
|
"div[data-datetime]",
|
|
|
|
|
"a.chat-transcript-channel",
|
|
|
|
|
]);
|
|
|
|
|
|
|
|
|
|
helper.registerOptions((opts, siteSettings) => {
|
|
|
|
|
opts.features["chat-transcript"] = !!siteSettings.chat_enabled;
|
|
|
|
|
});
|
|
|
|
|
|
|
|
|
|
helper.registerPlugin((md) => {
|
|
|
|
|
if (md.options.discourse.features["chat-transcript"]) {
|
|
|
|
|
md.block.bbcode.ruler.push("chat-transcript", chatTranscriptRule);
|
|
|
|
|
}
|
|
|
|
|
});
|
|
|
|
|
|
|
|
|
|
helper.buildCookFunction((opts, generateCookFunction) => {
|
|
|
|
|
if (!opts.discourse.additionalOptions) {
|
|
|
|
|
return;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
const chatAdditionalOpts = opts.discourse.additionalOptions.chat;
|
|
|
|
|
|
|
|
|
|
// we need to be able to quote images from chat, but the image rule is usually
|
|
|
|
|
// banned for chat messages
|
|
|
|
|
const markdownItRules =
|
|
|
|
|
chatAdditionalOpts.limited_pretty_text_markdown_rules.concat("image");
|
|
|
|
|
|
|
|
|
|
generateCookFunction(
|
|
|
|
|
{
|
|
|
|
|
featuresOverride: chatAdditionalOpts.limited_pretty_text_features,
|
|
|
|
|
markdownItRules,
|
FEATURE: Generic hashtag autocomplete lookup and markdown cooking (#18937)
This commit fleshes out and adds functionality for the new `#hashtag` search and
lookup system, still hidden behind the `enable_experimental_hashtag_autocomplete`
feature flag.
**Serverside**
We have two plugin API registration methods that are used to define data sources
(`register_hashtag_data_source`) and hashtag result type priorities depending on
the context (`register_hashtag_type_in_context`). Reading the comments in plugin.rb
should make it clear what these are doing. Reading the `HashtagAutocompleteService`
in full will likely help a lot as well.
Each data source is responsible for providing its own **lookup** and **search**
method that returns hashtag results based on the arguments provided. For example,
the category hashtag data source has to take into account parent categories and
how they relate, and each data source has to define their own icon to use for the
hashtag, and so on.
The `Site` serializer has two new attributes that source data from `HashtagAutocompleteService`.
There is `hashtag_icons` that is just a simple array of all the different icons that
can be used for allowlisting in our markdown pipeline, and there is `hashtag_context_configurations`
that is used to store the type priority orders for each registered context.
When sending emails, we cannot render the SVG icons for hashtags, so
we need to change the HTML hashtags to the normal `#hashtag` text.
**Markdown**
The `hashtag-autocomplete.js` file is where I have added the new `hashtag-autocomplete`
markdown rule, and like all of our rules this is used to cook the raw text on both the clientside
and on the serverside using MiniRacer. Only on the server side do we actually reach out to
the database with the `hashtagLookup` function, on the clientside we just render a plainer
version of the hashtag HTML. Only in the composer preview do we do further lookups based
on this.
This rule is the first one (that I can find) that uses the `currentUser` based on a passed
in `user_id` for guardian checks in markdown rendering code. This is the `last_editor_id`
for both the post and chat message. In some cases we need to cook without a user present,
so the `Discourse.system_user` is used in this case.
**Chat Channels**
This also contains the changes required for chat so that chat channels can be used
as a data source for hashtag searches and lookups. This data source will only be
used when `enable_experimental_hashtag_autocomplete` is `true`, so we don't have
to worry about channel results suddenly turning up.
------
**Known Rough Edges**
- Onebox excerpts will not render the icon svg/use tags, I plan to address that in a follow up PR
- Selecting a hashtag + pressing the Quote button will result in weird behaviour, I plan to address that in a follow up PR
- Mixed hashtag contexts for hashtags without a type suffix will not work correctly, e.g. #ux which is both a category and a channel slug will resolve to a category when used inside a post or within a [chat] transcript in that post. Users can get around this manually by adding the correct suffix, for example ::channel. We may get to this at some point in future
- Icons will not show for the hashtags in emails since SVG support is so terrible in email (this is not likely to be resolved, but still noting for posterity)
- Additional refinements and review fixes wil
2022-11-20 17:37:06 -05:00
|
|
|
|
hashtagLookup: opts.discourse.hashtagLookup,
|
|
|
|
|
hashtagTypesInPriorityOrder:
|
|
|
|
|
chatAdditionalOpts.hashtag_configurations["chat-composer"],
|
|
|
|
|
hashtagIcons: opts.discourse.hashtagIcons,
|
2022-11-02 09:41:30 -04:00
|
|
|
|
},
|
|
|
|
|
(customCookFn) => {
|
|
|
|
|
customMarkdownCookFn = customCookFn;
|
|
|
|
|
}
|
|
|
|
|
);
|
|
|
|
|
});
|
|
|
|
|
}
|