删除条目后，如何让RecyclerView的Observer返回当前筛选列表？

我在Android项目中用RecyclerView展示CardView列表，MainActivity通过Observer监听数据，用ListAdapter加载UI；同时搭建了ViewModel、Repository、DAO和Room数据库存储CardView数据，ViewModel里用MediatorLiveData处理排序和筛选操作。

现在遇到的问题：当列表筛选为仅显示“红色”CardView时，删除一个红色CardView，DAO已经正确删除了Room数据库中的对应数据，但MainActivity的Observer会自动触发onChanged()，此时UI加载的是删除后的完整列表，而非保持筛选后的红色CardView列表。我希望删除操作后仍显示筛选后的“红色”状态，请问哪里有问题？怎么修改让Observer返回当前筛选列表而非完整列表？

相关代码 #

MainActivity #

public class MainActivity extends AppCompatActivity {

    mViewModel = new ViewModelProvider(this).get(CardViewModel.class);

    mViewModel.getCards().observe(MainActivity.this, Cards -> {

        if (Cards != null && !Cards.isEmpty()) {
            mAdapter.submitList(Cards);
        }
    });

    // 筛选示例：用户点击TextView筛选主列表
    mViewModel.setSortOrder(CardRepository.SortOrder.DB_FILTRED);

    // 从Room数据库和UI中删除条目的方法
    public void removeItem(@NonNull final Card card) {
        mViewModel.delete(card);
    }    
}

CardViewModel #

public class CardViewModel extends AndroidViewModel {

    private static CardRepository repository;
    private final MediatorLiveData<List<Card>> cardsMediatrList = new MediatorLiveData<>();
    private LiveData<List<Card>> currSourceList;

    public CardViewModel(@NonNull Application application) {
        super(application);
        repository = new CardRepository(application);
        // 设置初始默认排序
        setSortOrder(DB_SORTORDER); 
    }

    public void delete(Card card) {
        repository.delete(card);
    } 

    // 获取所有卡片到RecyclerView列表
    public LiveData<List<Card>> getCards() {
        return cardsMediatrList;
    }

    public void setSortOrder(CardRepository.SortOrder newOrder) {
        // newOrder是Repository中SortOrder枚举的排序常量
        LiveData<List<Card>> newSourceList = repository.getSortedItems(newOrder);

        if (currSourceList != null) {
            cardsMediatrList.removeSource(currSourceList);
        }
        // 添加新数据源并赋值给currSourceList，以便后续切换筛选/排序时移除旧数据源
        currSourceList = newSourceList;

        // addSource()开始监听给定的LiveData，当数据源变化时调用onChanged观察者
        cardsMediatrList.addSource(currSourceList, cards -> {
            if (cards != null && !cards.isEmpty()) {
                cardsMediatrList.setValue(cards);
            }
        });
    }
}

CardRepository #

public class CardRepository {

    private final CardDao cardDao;

    public CardRepository(Application application) {
        CardRoomDatabase db = CardRoomDatabase.getDatabase(application);
        cardDao = db.cardDao();
    }

    public void delete(final Card card) {
        CardRoomDatabase.dbWriteExecutor.submit(() ->
            cardDao.deleteCard(card));
    } 

    public enum SortOrder {
        DB_SORTORDER,
        DB_FILTRED,
        ...
    }

    public LiveData<List<Card>> getSortedItems(SortOrder order) {
        switch (order) {
            case DB_SORTORDER:
                return cardDao.getAllCards();
            case DB_FILTRED:
                return cardDao.getFiltRedCards("RED");
            default:
                return cardDao.getAllCards();
        }
    }  
}

CardDao #

@Dao
public interface CardDao {    

    @Delete
    void deleteCard(Card card);   

    @Query("SELECT * FROM cards_table ORDER BY cardSortorder DESC")
    LiveData<List<Card>> getAllCards();  

    // 根据卡片类型RED筛选RecyclerView列表
    @Query("SELECT * FROM cards_table WHERE cardType = :cardType")
    LiveData<List<Card>> getFiltRedCards(String cardType);
}

核心问题分析 #

1. MediatorLiveData回调逻辑缺陷：原代码仅在筛选列表非空时更新数据，删除后列表为空时，cardsMediatrList不会触发更新，导致UI可能停留在旧数据或意外回退到默认列表。
2. 未持久化当前筛选状态：ViewModel未保存当前的筛选/排序状态，若因配置变化（如屏幕旋转）或内存回收导致ViewModel重建，会自动回到默认的完整列表排序。
3. ListAdapter提交逻辑受限：原代码仅在列表非空时提交数据，空列表无法触发UI清空操作。

修改方案 #

1. 在ViewModel中保存当前筛选状态 #

添加成员变量记录当前排序/筛选状态，确保数据库更新后仍维持当前筛选逻辑：

public class CardViewModel extends AndroidViewModel {
    private static CardRepository repository;
    private final MediatorLiveData<List<Card>> cardsMediatrList = new MediatorLiveData<>();
    private LiveData<List<Card>> currSourceList;
    // 新增：保存当前筛选状态
    private CardRepository.SortOrder currentSortOrder;

    public CardViewModel(@NonNull Application application) {
        super(application);
        repository = new CardRepository(application);
        // 初始化默认状态
        currentSortOrder = CardRepository.SortOrder.DB_SORTORDER;
        setSortOrder(currentSortOrder); 
    }

    public void setSortOrder(CardRepository.SortOrder newOrder) {
        // 更新并保存当前状态
        currentSortOrder = newOrder;
        LiveData<List<Card>> newSourceList = repository.getSortedItems(newOrder);

        if (currSourceList != null) {
            cardsMediatrList.removeSource(currSourceList);
        }
        currSourceList = newSourceList;

        // 修改：无论列表是否为空，都更新MediatorLiveData
        cardsMediatrList.addSource(currSourceList, cards -> {
            cardsMediatrList.setValue(cards);
        });
    }
}

2. 修复MainActivity的Observer逻辑 #

允许提交空列表，确保UI能正确反映筛选后的空状态：

mViewModel.getCards().observe(MainActivity.this, Cards -> {
    // 无论列表是否为空，都提交给ListAdapter
    mAdapter.submitList(Cards);
});

3. 可选：处理配置变化时的状态保存 #

若需要在屏幕旋转等场景下保留筛选状态，可使用SavedStateHandle持久化状态：

public class CardViewModel extends AndroidViewModel {
    private final SavedStateHandle savedStateHandle;
    private static final String KEY_SORT_ORDER = "key_sort_order";
    // ... 其他成员变量

    public CardViewModel(@NonNull Application application, SavedStateHandle savedStateHandle) {
        super(application);
        this.savedStateHandle = savedStateHandle;
        repository = new CardRepository(application);
        // 从SavedStateHandle恢复状态，无则用默认值
        currentSortOrder = savedStateHandle.get(KEY_SORT_ORDER) != null 
            ? savedStateHandle.get(KEY_SORT_ORDER) 
            : CardRepository.SortOrder.DB_SORTORDER;
        setSortOrder(currentSortOrder); 
    }

    public void setSortOrder(CardRepository.SortOrder newOrder) {
        currentSortOrder = newOrder;
        // 保存状态到SavedStateHandle
        savedStateHandle.set(KEY_SORT_ORDER, newOrder);
        // ... 其他逻辑
    }
}

内容的提问来源于stack exchange，提问作者AJW