71244f4a94
The 'Unmute' option is available in not-muted streams only when it is the current value. Add a 'Default' option. Available in both muted and not-muted streams. 'Default' corresponds to the 'INHERIT' visibility policy. Summary: * In muted streams: Four options: Mute, Default, Unmute, and Follow. * In not-muted streams: Three options: Mute, Default, and Follow. The fourth option, 'Unmute' is available only when it is the current value. Reason for conditional availability of 'Unmute' option: In a not-muted stream, 'Unmute' has no special significance. We only show 'Default' because both 'Default' and 'Unmute' has the same behaviour in the not-muted stream. This avoids the big design downside of showing this fourth nearly-identical option to users who are just in the normal default state of a normal topic within a normal stream We only show the 'Unmute' option in the not-muted stream to users. if they have followed a sequence of steps that led them to 'Unmute' state in a not-muted stream. For example: Mute a stream > Unmute a topic > Unmute the stream By doing so, we avoid destroying information. The user, when mutes the stream again, the topic will retain the 'Unmute' state. New icons for Mute, Default, Unmute, and Follow. |
||
|---|---|---|
| .. | ||
| icons | ||
| src | ||
| tools | ||
| .gitignore | ||
| .npmrc | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
The files in this subtree are part of the Zulip web frontend, and are also incorporated by the Zulip mobile app.
Note that the deployment cycles are different:
-
In the web app, this code is deployed in the same way as the rest of the web frontend: it's part of the server tree, and the browser gets it from the server, so the client is always running the same version the server just gave it.
-
In the mobile app, this code is deployed in the same way as the rest of the mobile app: it's bundled up into the app binary which is uploaded to app stores and users install on their devices. The client will be running the version built into their version of the mobile app, which may be newer, older, or simply different from the version on the server.
The mobile app always refers to a specific version of this code; changes to this code will appear in the mobile app only after a commit in the mobile app pulls them in.
To update the version of @zulip/shared on NPM, see the instructions in the mobile repo.