Utilize QStringLiteral where possible

The only exception are generated files and cases where
QLatin1String based overloads are used (e.g. during QString comparisons)

Change-Id: I6f36789fb8acb3b30c1dc1f8a920b118a979d74f
Reviewed-by: Kai Koehne <kai.koehne@digia.com>

1 files changed, 3 insertions, 3 deletions

diff --git a/src/nfc/qnearfieldtarget_emulator.cpp b/src/nfc/qnearfieldtarget_emulator.cpp
index 80953ce6..f261846f 100644
--- a/src/nfc/qnearfieldtarget_emulator.cpp
+++ b/src/nfc/qnearfieldtarget_emulator.cpp
@@ -212,15 +212,15 @@ void TagActivator::initialize()
     if (!tagMap.isEmpty())
         return;
 
-    QDirIterator nfcTargets(QDir::currentPath(), QStringList(QLatin1String("*.nfc")), QDir::Files);
+    QDirIterator nfcTargets(QDir::currentPath(), QStringList(QStringLiteral("*.nfc")), QDir::Files);
     while (nfcTargets.hasNext()) {
         const QString targetFilename = nfcTargets.next();
 
         QSettings target(targetFilename, QSettings::IniFormat);
 
-        target.beginGroup(QLatin1String("Target"));
+        target.beginGroup(QStringLiteral("Target"));
 
-        const QString tagType = target.value(QLatin1String("Type")).toString();
+        const QString tagType = target.value(QStringLiteral("Type")).toString();
 
         target.endGroup();