Page MenuHomePhabricator

[web] Use threadUIName instead of robotextName in ThreadSettingsModal
ClosedPublic

Authored by ashoat on Feb 4 2023, 6:24 PM.
Tags
None
Referenced Files
F3501947: D6592.id22005.diff
Fri, Dec 20, 3:52 AM
F3498890: D6592.diff
Thu, Dec 19, 9:50 PM
Unknown Object (File)
Wed, Dec 11, 9:09 PM
Unknown Object (File)
Tue, Dec 3, 4:30 AM
Unknown Object (File)
Sun, Dec 1, 9:08 AM
Unknown Object (File)
Nov 14 2024, 8:21 PM
Unknown Object (File)
Nov 14 2024, 8:21 PM
Unknown Object (File)
Nov 14 2024, 8:21 PM
Subscribers

Details

Summary

I'm about to deprecate robotextName. This diff updates ThreadSettingsModal to figure out a placeholder by resolving a version of the ThreadInfo without the name set.

Depends on D6591

Test Plan

Open and play around with ThreadSettingsModal, clear name to see placeholder

Screenshot 2023-02-04 at 9.45.30 PM.png (1×1 px, 174 KB)

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

ashoat requested review of this revision.Feb 4 2023, 6:40 PM

Make sure ThreadInfo.name isn't set when calling threadUIName

Revert accidental web/package.json change

This revision is now accepted and ready to land.Feb 5 2023, 10:45 AM