Chapril/xmpp.chapril.org-conversejs
Chapril/xmpp.chapril.org-conversejs
25
0
Fork 0
Code Issues Pull Requests Projects Releases Activity
5a3aaeb056
xmpp.chapril.org-conversejs/src/templates/chat_message.js

46 lines
2.3 KiB
JavaScript
Raw Normal View History

Fixes #2064 and move message markup into template After some back-and-forth, I think it's still better to keep markup in templates (instead of having them directly inside the components) becaues it makes it easier for people to modify Converse.js (at the expense of some developer ergonomics).
2020-06-11 15:27:45 +02:00
import { html } from "lit-html";
Fixes #2184: Headless build relies on locale directory Removed Jed from the headless build and instead let `__` call sprintf. It's now up to downstream users for `@converse/headless` to decide whether they want i18n support for the few translatable strings in that package and to implement it themselves.
2020-09-10 07:33:00 +02:00
import { __ } from '../i18n';
Fixes #2064 and move message markup into template After some back-and-forth, I think it's still better to keep markup in templates (instead of having them directly inside the components) becaues it makes it easier for people to modify Converse.js (at the expense of some developer ergonomics).
2020-06-11 15:27:45 +02:00
import { renderAvatar } from './../templates/directives/avatar';
Fixes #2064 (for real this time)
2020-06-11 17:03:59 +02:00
Fixes #2064 and move message markup into template After some back-and-forth, I think it's still better to keep markup in templates (instead of having them directly inside the components) becaues it makes it easier for people to modify Converse.js (at the expense of some developer ergonomics).
2020-06-11 15:27:45 +02:00
export default (o) => {
Fixes #2193. Translations called at the top of template files don't apply, since the trnaslations aren't yet fetched at that point.
2020-08-16 23:33:17 +02:00
const i18n_new_messages = __('New messages');
Fixes #2064 and move message markup into template After some back-and-forth, I think it's still better to keep markup in templates (instead of having them directly inside the components) becaues it makes it easier for people to modify Converse.js (at the expense of some developer ergonomics).
2020-06-11 15:27:45 +02:00
return html`
Don't use `date-separator` CSS class for the new messages indicator
2020-09-03 12:48:23 +02:00
${ o.is_first_unread ? html`<div class="message separator"><hr class="separator"><span class="separator-text">${ i18n_new_messages }</span></div>` : '' }
Fixes #2064 and move message markup into template After some back-and-forth, I think it's still better to keep markup in templates (instead of having them directly inside the components) becaues it makes it easier for people to modify Converse.js (at the expense of some developer ergonomics).
2020-06-11 15:27:45 +02:00
<div class="message chat-msg ${ o.getExtraMessageClasses() }"
data-isodate="${o.time}"
data-msgid="${o.msgid}"
data-from="${o.from}"
data-encrypted="${o.is_encrypted}">
MAM: Maintain scroll position during upwards infinite scroll
2020-10-13 05:57:27 +02:00
<!-- Anchor to allow us to scroll the message into view -->
<a id="${o.msgid}"></a>
Fixes #2064 and move message markup into template After some back-and-forth, I think it's still better to keep markup in templates (instead of having them directly inside the components) becaues it makes it easier for people to modify Converse.js (at the expense of some developer ergonomics).
2020-06-11 15:27:45 +02:00
${ o.shouldShowAvatar() ? renderAvatar(o.getAvatarData()) : '' }
<div class="chat-msg__content chat-msg__content--${o.sender} ${o.is_me_message ? 'chat-msg__content--action' : ''}">
Improve stying for /me messages Show the actions dropdown on the right, like with other messages, and don't wrap them.
2020-06-18 16:54:12 +02:00
${ !o.is_me_message ? html`
<span class="chat-msg__heading">
<span class="chat-msg__author">${o.username}</span>
${ o.renderAvatarByline() }
${ o.is_encrypted ? html`<span class="fa fa-lock"></span>` : '' }
</span>` : '' }
Fixes #2064 and move message markup into template After some back-and-forth, I think it's still better to keep markup in templates (instead of having them directly inside the components) becaues it makes it easier for people to modify Converse.js (at the expense of some developer ergonomics).
2020-06-11 15:27:45 +02:00
<div class="chat-msg__body chat-msg__body--${o.message_type} ${o.received ? 'chat-msg__body--received' : '' } ${o.is_delayed ? 'chat-msg__body--delayed' : '' }">
<div class="chat-msg__message">
Improve stying for /me messages Show the actions dropdown on the right, like with other messages, and don't wrap them.
2020-06-18 16:54:12 +02:00
${ (o.is_me_message) ? html`
Fix message reorder issue after edit (#2300) * keep message in place after edition by assigning previous message original timestamp * update time displayed to keep current behaviour * add test to check a message remains in the same position of the history after being edited * briefly describe pr changes in changelog
2020-10-23 15:07:56 +02:00
<time timestamp="${o.edited || o.time}" class="chat-msg__time">${o.pretty_time}</time>&nbsp;
Improve stying for /me messages Show the actions dropdown on the right, like with other messages, and don't wrap them.
2020-06-18 16:54:12 +02:00
<span class="chat-msg__author">${ o.is_me_message ? '**' : ''}${o.username}</span>&nbsp;` : '' }
Fixes #2064 and move message markup into template After some back-and-forth, I think it's still better to keep markup in templates (instead of having them directly inside the components) becaues it makes it easier for people to modify Converse.js (at the expense of some developer ergonomics).
2020-06-11 15:27:45 +02:00
${ o.is_retracted ? o.renderRetraction() : o.renderMessageText() }
</div>
<converse-message-actions
.chatview=${o.chatview}
.model=${o.model}
?correcting="${o.correcting}"
?editable="${o.editable}"
?is_retracted="${o.is_retracted}"
message_type="${o.message_type}"></converse-message-actions>
</div>
</div>
</div>`;
}
Reference in New Issue Copy Permalink