[ML 0.5/MVI.01] - Foundation & ViewModel Setup

🎯 The objective

Establish the MVI architecture for the MessageListFragment. This includes defining the state, events, and effects, and refactoring the ViewModel to follow the UDF (Unidirectional Data Flow) pattern. This is the prerequisite for all subsequent feature migrations.

🎒 Resources

ℹ️ List all relevant resources like BugZilla meta bugs, Figma files, Notion links and other files. These can be filled in later.

🦮 Rules of the Road

ℹ️ Initial definition of requirements and limitations, the scope of this feature and other potential considerations in order to keep the project narrow and focused.

🟢 In Scope

• Define the MessageList State
• Define the MessageList Events and Effects
• Adjust the MessageListViewModel to use a UDF approach

🔴 Out of Scope

• UI Redesign (unless specified)
• Migration of specific message actions (Move, Archive, etc.) - scheduled for later milestones.

🚧 Technical and/or Business Requirements

• Define the MessageList State:
  • The state must contain all data required to display content (Selected folder, List of messages, Swipe action preferences, Loading indicators, Search query, Sorting options).
• Define the Message List Events and Effects:
  • Define these before connecting real data to organize data requirements and dependencies.
• Adjust the MessageListViewModel:
  • Must extend the BaseViewModel.
  • Must expose a strong state that the UI relies on.
  • Must handle user events and update state accordingly, replacing the current limited implementation.