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
As a user creating a public room or changing an existing room to be public
I want to know if the room address is valid (does not have any invalid symbols) and available when I am editing it
So that I can correct my mistakes instantly; or be happy that the address I desire is available.
Since this a functionality that already exists in EW, the algorithm for checking for invalid symbols and other constraints can be borrowed from EW (or from any other implementation that exists today, as this is not a new problem). For reference: Matrix spec on identifiers.
Same goes for checking if the room address is available - the approach for this can be borrowed from EW and adjusted as necessary.
Designs:
TODO
Acceptance criteria
When user types a symbol that is not allowed they get a hint that there are invalid symbols.
When user corrects their mistakes and the address is valid, the hint for invalid symbols disappers.
When user enters an address that is valid but not available they get a hint that the address is already in use.
When user enters an address that is valid and available they get a confirmation that the address is available.
Size estimate
None
Dependencies
None
Out of scope
Nothing
Open questions
The content you are editing has changed. Please copy your edits and refresh the page.
mxandreas
changed the title
[Story] Check room's address for invalid symbols and uniqueness
[Story] Check room's address for invalid symbols and availability
Oct 16, 2024
Description
Since this a functionality that already exists in EW, the algorithm for checking for invalid symbols and other constraints can be borrowed from EW (or from any other implementation that exists today, as this is not a new problem). For reference: Matrix spec on identifiers.
Same goes for checking if the room address is available - the approach for this can be borrowed from EW and adjusted as necessary.
Designs:
Acceptance criteria
Size estimate
None
Dependencies
Out of scope
Open questions
Questions
Subtasks
Android
iOS
Rust
Other
The text was updated successfully, but these errors were encountered: