-
-
Notifications
You must be signed in to change notification settings - Fork 654
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set a stream web-public, in stream settings #5250
Labels
a-stream settings/subs
Creating streams, subscribing, editing settings
P1 high-priority
server release goal
Things we should try to coordinate with a major Zulip Server release.
webapp parity
Features that exist in the webapp that we need to port to mobile. We aren't aiming for full parity.
Comments
gnprice
added
the
webapp parity
Features that exist in the webapp that we need to port to mobile. We aren't aiming for full parity.
label
Feb 18, 2022
gnprice
added
the
a-stream settings/subs
Creating streams, subscribing, editing settings
label
Feb 18, 2022
gnprice
added
P1 high-priority
server release goal
Things we should try to coordinate with a major Zulip Server release.
labels
Apr 14, 2022
This was referenced Apr 14, 2022
chrisbobbe
added a commit
to chrisbobbe/zulip-mobile
that referenced
this issue
Apr 28, 2022
…itch For zulip#5250, we'll need to let the user choose one among more than two options. That'll call for a radio-button-style input, rather than a switch. So, make a new component InputRowRadioButtons, and use it for an input labeled "Privacy", replacing the SwitchRow input labeled "Private". And, to support that component, write and wire up another new component, SelectableOptionsScreen.
chrisbobbe
added a commit
to chrisbobbe/zulip-mobile
that referenced
this issue
May 4, 2022
…itch For zulip#5250, we'll need to let the user choose one among more than two options. That'll call for a radio-button-style input, rather than a switch. So, make a new component InputRowRadioButtons, and use it for an input labeled "Privacy", replacing the SwitchRow input labeled "Private". And, to support that component, write and wire up another new component, SelectableOptionsScreen.
chrisbobbe
added a commit
to chrisbobbe/zulip-mobile
that referenced
this issue
May 10, 2022
…itch For zulip#5250, we'll need to let the user choose one among more than two options. That'll call for a radio-button-style input, rather than a switch. So, make a new component InputRowRadioButtons, and use it for an input labeled "Privacy", replacing the SwitchRow input labeled "Private". And, to support that component, write and wire up another new component, SelectableOptionsScreen.
chrisbobbe
added a commit
to chrisbobbe/zulip-mobile
that referenced
this issue
May 10, 2022
…itch For zulip#5250, we'll need to let the user choose one among more than two options. That'll call for a radio-button-style input, rather than a switch. So, make a new component InputRowRadioButtons, and use it for an input labeled "Privacy", replacing the SwitchRow input labeled "Private". And, to support that component, write and wire up another new component, SelectableOptionsScreen.
chrisbobbe
added a commit
to chrisbobbe/zulip-mobile
that referenced
this issue
May 11, 2022
…itch For zulip#5250, we'll need to let the user choose one among more than two options. That'll call for a radio-button-style input, rather than a switch. So, make a new component InputRowRadioButtons, and use it for an input labeled "Privacy", replacing the SwitchRow input labeled "Private". And, to support that component, write and wire up another new component, SelectableOptionsScreen.
chrisbobbe
added a commit
to chrisbobbe/zulip-mobile
that referenced
this issue
May 13, 2022
…itch For zulip#5250, we'll need to let the user choose one among more than two options. That'll call for a radio-button-style input, rather than a switch. So, make a new component InputRowRadioButtons, and use it for an input labeled "Privacy", replacing the SwitchRow input labeled "Private". And, to support that component, write and wire up another new component, SelectableOptionsScreen.
This was referenced May 20, 2022
Closing as fixed by #5389. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
a-stream settings/subs
Creating streams, subscribing, editing settings
P1 high-priority
server release goal
Things we should try to coordinate with a major Zulip Server release.
webapp parity
Features that exist in the webapp that we need to port to mobile. We aren't aiming for full parity.
This is a follow-up on #5014, which was for displaying when a stream is web-public.
In the stream settings screen (which you get to e.g. via the "info" icon in the app bar when looking at the stream narrow), we offer a switch to make the stream private or public.
We should add the option to make it web-public. This probably means replacing the boolean switch UI with a UI to choose from a list.
While we're at it, this is probably a good prompt to add the concept of private streams with shared history (vs. private streams with protected history): #2683. So it'll be a choice between four options:
See the corresponding UI in the web app for comparison. Note there's kind of a lot of text accompanying each option -- which is probably necessary, because distinctions like "public" vs "web-public", or "shared history" vs "protected history", are a bit subtle.
The text was updated successfully, but these errors were encountered: