ts: Update extension of recently migrated '.js' files.

docs/subsystems/typing-indicators.md

@@ -121,7 +121,7 @@ as a concrete example.
 
 The events will come in to `web/src/server_events_dispatch.js`.
 The `stop` and `start` operations get further handled by
-`web/src/typing_events.js`.
+`web/src/typing_events.ts`.
 
 The main goal is then to triage which events should lead to
 display changes.

web/shared/src/typing_status.ts

@@ -124,7 +124,7 @@ export function maybe_ping_server(
  * See docs/subsystems/typing-indicators.md for detailed background on the
  * typing indicators system.
  *
- * @param {*} worker Callbacks for reaching the real world. See typing.js
+ * @param {*} worker Callbacks for reaching the real world. See typing.ts
  *   for implementations.
  * @param {*} new_recipient Depends on type of message being composed. If
  *   * Direct message: An Object containing id of users the DM being composed is addressed to

web/src/filter.ts

@@ -1139,7 +1139,7 @@ export class Filter {
         // The use case of this function is that we want
         // to know if a filter can start with a bucketing
         // data structure similar to the ones we have in
-        // unread.js to pre-filter ids, rather than apply
+        // unread.ts to pre-filter ids, rather than apply
         // a predicate to a larger list of candidate ids.
         //
         // (It's for optimization, basically.)

web/src/message_fetch.js

@@ -51,7 +51,7 @@ function process_result(data, opts) {
     const has_found_newest = opts.msg_list?.data.fetch_status.has_found_newest() ?? false;
 
     // In some rare situations, we expect to discover new unread
-    // messages not tracked in unread.js during this fetching process.
+    // messages not tracked in unread.ts during this fetching process.
     message_util.do_unread_count_updates(messages, true);
 
     // If we're loading more messages into the home view, save them to

web/src/stream_list.js

@@ -237,7 +237,7 @@ export function build_stream_list(force_rerender) {
         return;
     }
 
-    // The main logic to build the list is in stream_list_sort.js, and
+    // The main logic to build the list is in stream_list_sort.ts, and
     // we get five lists of streams (pinned/normal/muted_pinned/muted_normal/dormant).
     const stream_groups = stream_list_sort.sort_groups(streams, get_search_term());
 

web/src/typing.ts

@@ -26,7 +26,7 @@ type TypingAPIRequest = {op: "start" | "stop"} & (
 
 // This module handles the outbound side of typing indicators.
 // We detect changes in the compose box and notify the server
-// when we are typing.  For the inbound side see typing_events.js.
+// when we are typing.  For the inbound side see typing_events.ts.
 // See docs/subsystems/typing-indicators.md for more details.
 
 function send_typing_notification_ajax(data: TypingAPIRequest): void {

web/src/typing_events.ts

@@ -14,13 +14,13 @@ import * as typing_data from "./typing_data";
 // When another user is typing, we process the events here.
 //
 // We also handle the local event of re-narrowing.
-// (For the outbound code, see typing.js.)
+// (For the outbound code, see typing.ts.)
 
 // If number of users typing exceed this,
 // we render "Several people are typing..."
 const MAX_USERS_TO_DISPLAY_NAME = 3;
 
-// Note!: There are also timing constants in typing_status.js
+// Note!: There are also timing constants in typing_status.ts
 // that make typing indicators work.
 
 type UserInfo = {

web/src/ui_init.js

@@ -190,7 +190,7 @@ export function initialize_kitchen_sink_stuff() {
     //      This function is a historical dumping ground
     //      for lots of miscellaneous setup.  Almost all of
     //      the code here can probably be moved to more
-    //      specific-purpose modules like message_viewport.js.
+    //      specific-purpose modules like message_viewport.ts.
 
     const throttled_mousewheelhandler = _.throttle((_e, delta) => {
         // Most of the mouse wheel's work will be handled by the

web/tests/filter.test.js

@@ -1786,7 +1786,7 @@ test("navbar_helpers", () => {
 
     // TODO: test every single one of the "ALL" redirects from the navbar behaviour table
 
-    // incomplete and weak test cases just to restore coverage of filter.js
+    // incomplete and weak test cases just to restore coverage of filter.ts
     const complex_term = [
         {operator: "stream", operand: "foo"},
         {operator: "topic", operand: "bar"},

web/tests/message_store.test.js

@@ -220,7 +220,7 @@ test("errors", ({disallow_rewire}) => {
     blueslip.expect("error", "Unknown user id", 1); // From person.js
 
     // Expect each to throw two blueslip errors
-    // One from message_store.js, one from person.js
+    // One from message_store.ts, one from person.js
     const emails = message_store.get_pm_emails(message);
     assert.equal(emails, "?");