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
In the current implementation we give the room name as the id of the room element. But incase the room name has spaces the room id is then set with spaces, which wrong. So when there are space in the room name, the room id should be set with the spaces being replaced with - . If the room name is Hello World, id should be Hello-World .
This is a critical change as room id is being used a lot of places and the change should ensure that nothing gets broken.
The text was updated successfully, but these errors were encountered:
@sesamechicken I think that's something the backend should handle ideally. Because if a user creates a room with and we show them it replaced with -, it's not good UX.
The user should be able to create a room with spaces. You can, in the front end code, set the ID's as the room name with the spaces replaced with dashes so you have qualified selectors. Does that make sense?
In the current implementation we give the room name as the id of the room element. But incase the room name has spaces the room id is then set with spaces, which wrong. So when there are space in the room name, the room id should be set with the spaces being replaced with
-
. If the room name isHello World
, id should beHello-World
.This is a critical change as room id is being used a lot of places and the change should ensure that nothing gets broken.
The text was updated successfully, but these errors were encountered: