You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When first creating a PublicRoom system, the following will display for the name: For the channel_name_template, enter a string, with {num} contained if you want it to be replaced with the number of active VCs.
However, when editing the name of the system, you will be met with the following: Enter a string, with {creator} contained if you want it to be replaced with the VC creator's display name.
{creator} does not work with PublicRooms. However, it does work with PrivateRooms. The best solution in this case would be to make both options work on both systems. As both can identify the invoker of the channel creation.
The text was updated successfully, but these errors were encountered:
Thanks for reporting this! I think I just forgot to replace a docstring, as PrivateRooms was created first and quite a bit of code was reused between them. For making the {creator} option work on both of them, I don't think I will be adding that as I don't think the point of PublicRooms reflects having a room creator's name in the channel. However, I will definitely be fixing that docstring to have the correct instructions (that should be pushed in a few minutes, at which point I will also close this issue).
Obi-Wan3
changed the title
PublicRooms Displays Incorrect Information when Editing Name
[PublicRooms] Bug: Incorrect Docstring for Edit Name
Apr 6, 2021
When first creating a PublicRoom system, the following will display for the name:
For the channel_name_template, enter a string, with {num} contained if you want it to be replaced with the number of active VCs.
However, when editing the name of the system, you will be met with the following:
Enter a string, with {creator} contained if you want it to be replaced with the VC creator's display name.
{creator} does not work with PublicRooms. However, it does work with PrivateRooms. The best solution in this case would be to make both options work on both systems. As both can identify the invoker of the channel creation.
The text was updated successfully, but these errors were encountered: