Fix "subjects" in JS comments. Say "topics" instead.

This commit is contained in:
Steve Howell
2016-10-28 10:07:25 -07:00
committed by Tim Abbott
parent 5fd71a6381
commit eb64b32bc8
3 changed files with 3 additions and 3 deletions

View File

@@ -362,7 +362,7 @@ exports.by_subject = function (target_id, opts) {
// don't use current_msg_list as it won't work for muted messages or for out-of-narrow links
var original = message_store.get(target_id);
if (original.type !== 'stream') {
// Only stream messages have subjects, but the
// Only stream messages have topics, but the
// user wants us to narrow in some way.
exports.by_recipient(target_id, opts);
return;

View File

@@ -279,7 +279,7 @@ function get_topic_suggestions(query_operators) {
topics = topics.slice(0, 10);
// Just use alphabetical order. While recency and read/unreadness of
// subjects do matter in some contexts, you can get that from the left sidebar,
// topics do matter in some contexts, you can get that from the left sidebar,
// and I'm leaning toward high scannability for autocompletion. I also don't
// care about case.
topics.sort();

View File

@@ -500,7 +500,7 @@ exports.update_dom_with_unread_counts = function (counts) {
set_count("stream", stream, count);
});
// counts.subject_count maps streams to hashes of subjects to counts
// counts.subject_count maps streams to hashes of topics to counts
counts.subject_count.each(function (subject_hash, stream) {
var stream_li = get_filter_li('stream', stream);
subject_hash.each(function (count, subject) {