{"version":"2.1.271","anchor":"session-display-name-tracking-records-the-user-typed-name-ea","canonical_anchor":"session-display-name-tracking-records-the-user-typed-name-ea","heading":"Session display-name tracking records the user-typed name earlier, plus a helper to recall it","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/session-display-name-tracking-records-the-user-typed-name-ea","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Session display-name tracking records the user-typed name earlier, plus a helper to recall it\n\nSession names typed by the user are now recorded earlier, and a new helper can recall that typed name\n\n**What**\n\nThe code that records a user-typed session or thread name now saves it before checking whether a name-recheck is even needed, rather than only after passing that check as before. A new helper function can look up that user-typed name, but only returns it if it still matches the source (user-typed or a collision) of the session's current derived name.\n\n**Why**\n\nRecording the typed name earlier means it's captured even in cases that would have previously skipped past that point, and the new helper lets other code confirm a name is still the one the user actually typed rather than one derived automatically.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}