From 1812c077d6461b3e9fb865f47cffafc3c179e136 Mon Sep 17 00:00:00 2001 From: Christian Mollekopf Date: Tue, 19 Jan 2016 14:07:17 +0100 Subject: Disambiguate between what we want to flush Even though the implementation is still exactly the same --- tests/maildirresourcetest.cpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'tests') diff --git a/tests/maildirresourcetest.cpp b/tests/maildirresourcetest.cpp index 146489d..ec4f6a4 100644 --- a/tests/maildirresourcetest.cpp +++ b/tests/maildirresourcetest.cpp @@ -321,7 +321,7 @@ private Q_SLOTS: auto mail = mails.first(); return Store::remove(*mail) - .then(Store::flushMessageQueue(query.resources)) //The change needs to be replayed already + .then(Store::flushReplayQueue(query.resources)) //The change needs to be replayed already .then(Resources::inspect(Resources::Inspection::ExistenceInspection(*mail, false))); }) .then([](){}); @@ -357,7 +357,7 @@ private Q_SLOTS: mail->setProperty("unread", true); auto inspectionCommand = Resources::Inspection::PropertyInspection(*mail, "unread", true); return Store::modify(*mail) - .then(Store::flushMessageQueue(query.resources)) //The change needs to be replayed already + .then(Store::flushReplayQueue(query.resources)) //The change needs to be replayed already .then(Resources::inspect(inspectionCommand)); }) .then([](){}); -- cgit v1.2.3