Remove unsupported message statuses from nodejs

Signed-off-by: Patrik Stas <patrik.stas@absa.africa>
hyperledger · Jul 14, 2022 · f6d055d · f6d055d
1 parent 70c371d
commit f6d055d
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/agents/node/vcxagent-core/src/utils/messages.js b/agents/node/vcxagent-core/src/utils/messages.js
@@ -28,10 +28,10 @@ async function parseDownloadMessagesResult (msgs) {
 
 module.exports.getMessagesForConnection = async function getMessagesForConnection (
   connection,
-  filterStatuses = ['MS-102', 'MS-103', 'MS-104', 'MS-105', 'MS-106'],
+  filterStatuses = ['MS-103', 'MS-106'],
   filterUids = []
 ) {
-  filterStatuses = filterStatuses || ['MS-102', 'MS-103', 'MS-104', 'MS-105', 'MS-106'] // explicit null or undefined interpreted as "no filter"
+  filterStatuses = filterStatuses || ['MS-103', 'MS-106'] // explicit null or undefined interpreted as "no filter"
   const downloadInstructions = {
     status: await maybeJoinWithComma(filterStatuses),
     uids: await maybeJoinWithComma(filterUids)