Discource-C
/
discourse
mirror of https://github.com/discourse/discourse.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
discourse/app/serializers/user_option_serializer.rb

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

63 lines
2.0 KiB
Ruby
Raw Normal View History

DEV: enable frozen string literal on all files This reduces chances of errors where consumers of strings mutate inputs and reduces memory usage of the app. Test suite passes now, but there may be some stuff left, so we will run a few sites on a branch prior to merging
2019-05-02 18:17:27 -04:00
# frozen_string_literal: true
PERF: shift most user options out of the user table As it stands we load up user records quite frequently on the topic pages, this in turn pulls all the columns for the users being selected, just to discard them after they are loaded New structure keeps all options in a discrete table, this is better organised and allows us to easily add more column without worrying about bloating the user table
2016-02-16 23:46:19 -05:00
class UserOptionSerializer < ApplicationSerializer
attributes :user_id,
:mailing_list_mode,
FEATURE: More granular mailing list mode (#4068) * Rearrange frontend to account for mailing list mode * Allow update of user preference for mailing list frequency * Add mailing list frequency estimate * Simplify frequency estimate; disable activity summary for mailing list mode * Remove combined updates * Add specs for enqueue mailing list mode job * Write mailing list method for mailer * Fix linting error * Account for stale topics * Add translations for default mailing list setting * One query for mailing list topics * Fix failing spec * WIP * Flesh out html template * First pass at text-based mailing list summary * Add user avatar * Properly format posts for mailing list * Move make_all_links_absolute into Email::Styles * Apply first_seen_at to user * Send mailing list email summary hourly based on first_seen_at * Branch and test cleanup * Use existing mailing list mode estimate * Fix failing specs
2016-05-21 09:17:54 -04:00
:mailing_list_mode_frequency,
PERF: shift most user options out of the user table As it stands we load up user records quite frequently on the topic pages, this in turn pulls all the columns for the users being selected, just to discard them after they are loaded New structure keeps all options in a discrete table, this is better organised and allows us to easily add more column without worrying about bloating the user table
2016-02-16 23:46:19 -05:00
:email_digests,
FEATURE: add more granular user option levels for email notifications (#7143) Migrates email user options to a new data structure, where `email_always`, `email_direct` and `email_private_messages` are replace by * `email_messages_level`, with options: `always`, `only_when_away` and `never` (defaults to `always`) * `email_level`, with options: `always`, `only_when_away` and `never` (defaults to `only_when_away`)
2019-03-15 10:55:11 -04:00
:email_level,
:email_messages_level,
PERF: shift most user options out of the user table As it stands we load up user records quite frequently on the topic pages, this in turn pulls all the columns for the users being selected, just to discard them after they are loaded New structure keeps all options in a discrete table, this is better organised and allows us to easily add more column without worrying about bloating the user table
2016-02-16 23:46:19 -05:00
:external_links_in_new_tab,
FEATURE: User selectable color schemes (#10544)
2020-08-28 10:36:52 -04:00
:color_scheme_id,
FEATURE: Allow users to opt out of automatic dark mode (#10377)
2020-08-06 09:45:37 -04:00
:dark_scheme_id,
PERF: shift most user options out of the user table As it stands we load up user records quite frequently on the topic pages, this in turn pulls all the columns for the users being selected, just to discard them after they are loaded New structure keeps all options in a discrete table, this is better organised and allows us to easily add more column without worrying about bloating the user table
2016-02-16 23:46:19 -05:00
:dynamic_favicon,
:enable_quoting,
FEATURE: Add user preference to disable smart lists (#29434) Followup 30fdd7738ec942126bb055c9a6a8d69ddffba2da Adds a new site setting and corresponding user preference to disable smart lists. By default they are enabled, because this is a better experience for most users. A small number of users would prefer to not have this enabled. Smart lists automatically append new items to each list started in the composer when enter is pressed. If enter is pressed on an empty list item, it is cleared. This setting will be removed when the new composer is complete.
2024-10-28 00:18:15 -04:00
:enable_smart_lists,
FEATURE: add support for defer topic functionality This feature allows end users to "defer" topics by marking them unread The functionality is default disabled. This also introduces the new site setting default_other_enable_defer: to enable this by default on new user accounts.
2019-05-31 01:43:17 -04:00
:enable_defer,
FEATURE: More digest email frequency options. Digests can be sent as often as every 30 minutes.
2016-03-02 15:26:27 -05:00
:digest_after_minutes,
PERF: shift most user options out of the user table As it stands we load up user records quite frequently on the topic pages, this in turn pulls all the columns for the users being selected, just to discard them after they are loaded New structure keeps all options in a discrete table, this is better organised and allows us to easily add more column without worrying about bloating the user table
2016-02-16 23:46:19 -05:00
:automatically_unpin_topics,
PERF: move 3 more option columns out of the user table
2016-02-18 00:57:22 -05:00
:auto_track_topics_after_msecs,
Add notification level user preference when replying to a topic
2016-09-30 12:36:43 -04:00
:notification_level_when_replying,
FEATURE: allow users to control how many previous replies they get - always means we always send previous replies with every email - never means we do not - "unless previously sent" ... is the default, in which we only email you each reply once The default_email_previous_replies site setting can control this toggle
2016-02-18 21:56:52 -05:00
:new_topic_duration_minutes,
FEATURE: add "email in-reply-to user option" We no longer include previous replies as "context", instead we include and excerpt of the post being replied to at the bottom of notifications, this information was previously missing. Users may opt in to emailing previous replies if they wish or opt out of "in-reply-to" which makes sense in some email clients that are smarter about displaying a tree of replies.
2016-02-25 08:05:40 -05:00
:email_previous_replies,
FEATURE: users can select how frequently they are notified on likes - first time - first time and daily (default) - always
2016-03-02 07:16:52 -05:00
:email_in_reply_to,
FEATURE: add option to include topics from trust level 0 users in digest emails
2016-03-17 17:35:23 -04:00
:like_notification_frequency,
FEATURE: theme selection is now global per-user
2017-05-12 12:41:26 -04:00
:include_tl0_in_digests,
FEATURE: Groundwork for user-selectable theme components * Phase 0 for user-selectable theme components - Drops `key` column from the `themes` table - Drops `theme_key` column from the `user_options` table - Adds `theme_ids` (array of ints default []) column to the `user_options` table and migrates data from `theme_key` to the new column. - Removes the `default_theme_key` site setting and adds `default_theme_id` instead. - Replaces `theme_key` cookie with a new one called `theme_ids` - no longer need Theme.settings_for_client
2018-07-12 00:18:21 -04:00
:theme_ids,
FEATURE: Allow users to disable new PMs. https://meta.discourse.org/t/is-it-possible-to-disable-private-messaging-for-a-specific-user/46391
2017-10-06 03:56:58 -04:00
:theme_key_seq,
:allow_private_messages,
FEATURE: Allow List for PMs (#10270) * FEATURE: Allow List for PMs This feature adds a new user setting that is disabled by default that allows them to specify a list of users that are allowed to send them private messages. This way they don't have to maintain a large list of users they don't want to here from and instead just list the people they know they do want. Staff will still always be able to send messages to the user. * Update PR based on feedback
2020-07-20 17:23:49 -04:00
:enable_allowed_pm_users,
FEATURE: Allow the user to select a custom home page (#5268) * Add user_home configuration option * Use the new user_home preference to actually show the right home page * Fix trailing whitespace * Update user_option_serializer.rb * Fix JavaScript default homepage tests * Use an object instead of a giant switch * Remove trailing whitespace * Make the default `user_home` set to `null` instead of `0` * Rename user_home to homepage_id
2017-11-09 14:45:19 -05:00
:homepage_id,
FEATURE: Allow the base font size to be changed on a per-user basis (#6859)
2019-01-14 08:21:46 -05:00
:hide_profile_and_presence,
FEATURE: Allow overriding text size from a different device (#6955) This brings the feature in line with the theme selection system
2019-01-28 06:19:50 -05:00
:text_size,
FEATURE: Add user preference for title counter mode (#7364)
2019-04-11 19:02:18 -04:00
:text_size_seq,
FEATURE: Add timezone to core user_options (#8380) * Add timezone to user_options table * Also migrate existing timezone values from UserCustomField, which is where the discourse-calendar plugin is storing them * Allow user to change their core timezone from Profile * Auto guess & set timezone on login & invite accept & signup * Serialize user_options.timezone for group members. this is so discourse-group-timezones can access the core user timezone, as it is being removed in discourse-calendar. * Annotate user_option with timezone * Validate timezone values
2019-11-24 19:49:27 -05:00
:title_count_mode,
FIX: Remove user_option saving for bookmark auto delete pref (#19476) We were changing the user's user_option.bookmark_auto_delete_preference to whatever they changed it to in the bookmark modal to use as default for future bookmarks. However this was leading to a lot of confusion since if you wanted to set it for one bookmark you had to remember to change it back on the next one. This commit removes that automatic functionality, and instead moves the bookmark auto delete preference to User Preferences > Interface in an explicit dropdown.
2022-12-15 17:50:31 -05:00
:bookmark_auto_delete_preference,
FEATURE: add new user option `skip_new_user_tips`. (#10437) And add new site setting `default_other_skip_new_user_tips` in user preferences category.
2020-08-14 09:40:56 -04:00
:timezone,
FEATURE: save local date to calendar (#14486) It allows saving local date to calendar. Modal is giving option to pick between ics and google. User choice can be remembered as a default for the next actions.
2021-10-05 23:11:52 -04:00
:skip_new_user_tips,
:default_calendar,
FEATURE: Add button to reset seen popups (#18586)
2022-10-19 21:06:39 -04:00
:oldest_search_log_date,
FEATURE: Split navigation preference for count and behavior of sidebar links (#22203) This PR splits up the preference that controls the count vs dot and destination of sidebar links, which is really hard to understand, into 2 simpler checkboxes: The new preferences/checkboxes are off by default, but there are database migrations to switch the old preference to the new ones so that existing users don't have to update their preferences to keep their preferred behavior of sidebar links when this changed is rolled out. Internal topic: t/103529.
2023-06-22 12:04:13 -04:00
:seen_popups,
:sidebar_link_to_filtered_list,
FEATURE: allow user to override watched_precedence_over_muted setting (#22340) Recently, site setting watched_precedence_over_muted was introduced - https://github.com/discourse/discourse/pull/22252 In this PR, we are allowing users to override it. The option is only displayed when the user has watched categories and muted tags, or vice versa.
2023-07-04 01:08:29 -04:00
:sidebar_show_count_of_new_items,
FEATURE: Silence Close Notifications User Setting (#26072) This change creates a user setting that they can toggle if they don't want to receive unread notifications when someone closes a topic they have read and are watching/tracking it.
2024-03-08 17:14:46 -05:00
:watched_precedence_over_muted,
:topics_unread_when_closed
DEV: Do not include method definitions in serializer `attributes` These accidental inclusions are mostly no-ops (because the method name is also included as an explicit symbol). The mistakes were made more obvious because syntax_tree adjusted the indentation of these methods
2023-01-09 08:59:43 -05:00
def auto_track_topics_after_msecs
object.auto_track_topics_after_msecs || SiteSetting.default_other_auto_track_topics_after_msecs
end
PERF: move 3 more option columns out of the user table
2016-02-18 00:57:22 -05:00
Add notification level user preference when replying to a topic
2016-09-30 12:36:43 -04:00
def notification_level_when_replying
object.notification_level_when_replying ||
SiteSetting.default_other_notification_level_when_replying
end
PERF: move 3 more option columns out of the user table
2016-02-18 00:57:22 -05:00
def new_topic_duration_minutes
object.new_topic_duration_minutes || SiteSetting.default_other_new_topic_duration_minutes
end
FEATURE: Groundwork for user-selectable theme components * Phase 0 for user-selectable theme components - Drops `key` column from the `themes` table - Drops `theme_key` column from the `user_options` table - Adds `theme_ids` (array of ints default []) column to the `user_options` table and migrates data from `theme_key` to the new column. - Removes the `default_theme_key` site setting and adds `default_theme_id` instead. - Replaces `theme_key` cookie with a new one called `theme_ids` - no longer need Theme.settings_for_client
2018-07-12 00:18:21 -04:00
def theme_ids
object.theme_ids.presence || [SiteSetting.default_theme_id]
FEATURE: theme selection is now global per-user
2017-05-12 12:41:26 -04:00
end
PERF: shift most user options out of the user table As it stands we load up user records quite frequently on the topic pages, this in turn pulls all the columns for the users being selected, just to discard them after they are loaded New structure keeps all options in a discrete table, this is better organised and allows us to easily add more column without worrying about bloating the user table
2016-02-16 23:46:19 -05:00
end