frontend: Seperate out info on accessing emails to template.

This commit is contained in:
Vishnu Ks
2017-10-02 21:26:20 +00:00
committed by Tim Abbott
parent 2267f09813
commit 0c35bd60cf
3 changed files with 9 additions and 6 deletions

View File

@@ -504,6 +504,11 @@ function render(template_name, args) {
assert.equal(a.text(), "Narrow to here"); assert.equal(a.text(), "Narrow to here");
}()); }());
(function dev_env_email_access() {
var html = render('dev_env_email_access');
global.write_handlebars_output("dev_env_email_access", html);
}());
(function draft_table_body() { (function draft_table_body() {
var args = { var args = {
drafts: [ drafts: [

View File

@@ -76,12 +76,8 @@ exports.initialize = function () {
invitee_emails.val(''); invitee_emails.val('');
if (page_params.development_environment) { if (page_params.development_environment) {
// line-wrapped to avoid the i18n linter, since we don't want to translate this. var email_msg = templates.render('dev_env_email_access');
$('#dev_env_msg').html( $('#dev_env_msg').html(email_msg).addClass('alert-info').show();
'In the Zulip development environment, outgoing emails can be accessed by opening ' +
'<a href="/emails">/emails</a>. They are also printed to the run-dev.py console.')
.addClass('alert-info')
.show();
} }
}, },

View File

@@ -0,0 +1,2 @@
In the development environment, outgoing emails are logged to
<a href="/emails">/emails</a>.