The user was cached in BaseSettingsActivity.kt, so
DisplayNameAndSignatureFragment.kt was not able to get updated values,
until the user is updated in BaseSettingsActivity.kt
MAILAND-2340
MAILAND-1863
MAILAND-2017
Many methods were used only for clean up and have been replaced with new Dao in ClearUserData.kt, other methods were used only in CounterDaoTest.kt
MAILAND-2272
Now we use the mail settings flow from core, we observe it in the mailbox so it is reflected for the initial fetch of settings and after a change from the settings activity.
MAILAND-2032
The order of account settings has been changed, the snooze settings are
now under the mailbox settings.
The setting item's SetValue() has been updated to notify the adapter of the
change, that allows to set it asynchronously.
MAILAND-2086
This reverts commit 54820ceb
Revert "Extracted logic from SwipeChooserActivity to a view model"
This reverts commit d2ed89c5
Revert "Swipe actions were showing the default actions instead of actions set up by the user"
This reverts commit cb252e9c
Revert "Rename and move use case that handles changes to view mode"
This reverts commit 88ef4deb
Revert "When you would change the view mode from conversations to messages or the other way around and go back to the mailbox the setting change was ignored. Now on this action we clear the messages and conversation tables and reload the mailbox. We rely on the mail settings core module to persist the change."
This reverts commit 737c11a2
Revert "Update core libraries to introduce mail settings module"
This reverts commit 0f4cb3b3
Revert "Moved Conversation.kt model inside domain/model directory"
This reverts commit 2c8508c8
MAILAND-2032
MAILAND-2087
When you would change the view mode from conversations to messages or the other way around and go back to the mailbox the setting change was ignored. Now on this action we clear the messages and conversation tables and reload the mailbox. We rely on the mail settings core module to persist the change.
MAILAND-2087
Rename and move use case that handles changes to view mode
Swipe actions were showing the default actions instead of actions set up by the user
Now we use the mail settings flow from core, we observe it in the mailbox so it is reflected for the initial fetch of settings and after a change from the settings activity.
MAILAND-2032
Extracted logic from SwipeChooserActivity to a view model
Extracted logic from AccountSettingsActivity.kt to a view model
Change mobile signature to mobile footer everywhere and add text view with info explaining the feature
Fix display name input field to be single line
Fix title of DisplayNameAndSignatureFragment
Such flag was used to differentiate between messages that were coming
from "Search" (being the transient ones) and those that weren't.
This conditional being performed in many places was adding a lot of
noise and not really bringing any value, as the same behaviour can be
achieved by not storing messages from search in the first place.