Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/web/templates/stream_settings/new_stream_user.hbs

14 lines
486 B
Handlebars
Raw Normal View History

stream create: Overhaul create-stream add-subscribers UI. The most notable change here is that when you are adding subscribers to a stream as part of creating the stream, you can now use the same essential pill-based UI for adding users as we do when you edit subscribers for an existing stream. We don't try to exactly mimic the edit-stream UI or implementation, since when you are adding subscribers during create-stream, we are just updating a list in memory, whereas in the edit-stream UI, we immediately send info to the server. Fixes #20499
2022-02-08 18:56:40 +01:00
<tr>
stream_settings: Convert name to pills. Convert anchor tag to pills containing an image/avatar and username within both existing and new stream subscriber member lists and group member lists using the new user_display_only_pill.hbs template. If user has long username that breaks the UI, overflow is handled with ellipsis. add a context class (panel_subscriber_member_list) to add 'padding 5px'to 'pill_value' for stream subscriber member list and group member list. To retrieve an avatar of a user add a 'img_src: people.small_avatar_url_for_person(user/person)' field in 'stream_editsubscriber.js', 'user_group_edit_members.js', 'stream_create_subscribers.js' and 'user_group_create_members.js'. Fixes: #25724.
2024-01-08 15:39:20 +01:00
<td class="panel_subscriber_member_list">
{{> ../user_display_only_pill display_value=full_name}}
stream create: Overhaul create-stream add-subscribers UI. The most notable change here is that when you are adding subscribers to a stream as part of creating the stream, you can now use the same essential pill-based UI for adding users as we do when you edit subscribers for an existing stream. We don't try to exactly mimic the edit-stream UI or implementation, since when you are adding subscribers during create-stream, we are just updating a list in memory, whereas in the edit-stream UI, we immediately send info to the server. Fixes #20499
2022-02-08 18:56:40 +01:00
</td>
settings: Use user-level email_address_visibility setting in UI. This commit basically updates the frontend code to directly use delivery_email field instead of functions like show_email or email_for_user_settings at places where we want to show email. We can do this change since we recently updated the server code to always pass "delivery_email" code in the user objects with its value being null if the real email is not accessible. Showing email or "hidden" or nothing at various places in UI like in users list, subscriber list, user profile popover and modal is same as before. Major points - - Removed show_email and email_for_user_settings functions since we directly use delivery_email field now as explained above. - While sorting by emails in the users list, users with real emails hidden are always shown in last when sorting alphabetically and at the top when sorting reverse alphabetically. Also, those users with real emails hidden, are sorted by name among themselves. As we did before, we do not allow sorting by email when all emails are hidden. - There is no change in typeahead behavior at this point. We either hide the email completely or show the real or fake email based on user level setting. - Added code to handle delivery_email events and appropriately add/remove delivery_email field from person objects.
2021-10-26 15:43:39 +02:00
{{#if email}}
stream create: Overhaul create-stream add-subscribers UI. The most notable change here is that when you are adding subscribers to a stream as part of creating the stream, you can now use the same essential pill-based UI for adding users as we do when you edit subscribers for an existing stream. We don't try to exactly mimic the edit-stream UI or implementation, since when you are adding subscribers during create-stream, we are just updating a list in memory, whereas in the edit-stream UI, we immediately send info to the server. Fixes #20499
2022-02-08 18:56:40 +01:00
<td class="subscriber-email">{{email}}</td>
{{else}}
<td class="hidden-subscriber-email">{{t "(hidden)"}}</td>
{{/if}}
<td>
stream creation: Change the color of remove button in subscribers tab. This button was red, which is appropriate when modifying an existing stream, since that's a potentially disruptive action, but not appropriate in the context of previewing subscribers for a new stream being created. Fixes: #21863.
2022-06-28 22:11:35 +02:00
<button {{#if disabled}} disabled="disabled"{{/if}} data-user-id="{{user_id}}" class="remove_potential_subscriber button small rounded white">{{t 'Remove' }}</button>
stream create: Overhaul create-stream add-subscribers UI. The most notable change here is that when you are adding subscribers to a stream as part of creating the stream, you can now use the same essential pill-based UI for adding users as we do when you edit subscribers for an existing stream. We don't try to exactly mimic the edit-stream UI or implementation, since when you are adding subscribers during create-stream, we are just updating a list in memory, whereas in the edit-stream UI, we immediately send info to the server. Fixes #20499
2022-02-08 18:56:40 +01:00
</td>
</tr>