fix: cli language & params

Author: rflechtner

src/cli/createDidConfig.ts

@@ -84,21 +84,20 @@ async function write(toWrite: unknown, outPath?: string) {
 async function run() {
   await yargs(process.argv.slice(2))
     .command(
-      'fromCredentials <...pathToCredential>',
+      'fromCredentials [pathToCredential..]',
       'create a Did Configuration Resource from one or more existing Domain Linkage Credentials',
       (ygs) =>
-        ygs.options(commonOpts).positional('pathsToCredential', {
+        ygs.options(commonOpts).positional('pathToCredential', {
           describe: 'Path to a json file containing the credential presentation',
           type: 'string',
           demandOption: true,
           array: true,
         }),
-      async ({ pathsToCredential, outFile }) => {
-        const credentials: DomainLinkageCredential[] = []
-        await Promise.all(
-          pathsToCredential.map(async (pathToCredential) => {
+      async ({ pathToCredential, outFile }) => {
+        const credentials: DomainLinkageCredential[] = await Promise.all(
+          pathToCredential.map(async (pathToCredential) => {
             try {
-              credentials.push(JSON.parse(await readFile(pathToCredential, { encoding: 'utf-8' })))
+              return JSON.parse(await readFile(pathToCredential, { encoding: 'utf-8' }))
             } catch (cause) {
               throw new Error(`Cannot parse file ${pathToCredential}`, { cause })
             }
@@ -117,14 +116,16 @@ async function run() {
     )
     .command(
       'credentialOnly',
-      'issue a new Kilt Credential Presentation for use in a Did Configuration Resource',
+      'issue a new Domain Linkage Credential for use in a Did Configuration Resource',
       {
         ...createCredentialOpts,
         ...commonOpts,
         proofType: {
           alias: 'p',
           choices: [DataIntegrity.PROOF_TYPE, KILT_SELF_SIGNED_PROOF_TYPE] as const,
           default: KILT_SELF_SIGNED_PROOF_TYPE,
+          describe:
+            'Which proof type to use in the credential. DataIntegrity is the more modern proof type, but might not be accepted by all extensions yet. Did Configuration Resources can contain multiple credentials, though.',
         },
       },
       async ({ origin, seed, keyType, wsAddress, outFile, did, proofType }) => {
@@ -135,7 +136,7 @@ async function run() {
     )
     .command(
       '$0',
-      'create a Did Configuration Resource from a freshly issued Verifiable Credential',
+      'create a Did Configuration Resource containing newly issued Domain Linkage Credentials',
       { ...createCredentialOpts, ...commonOpts },
       async ({ origin, seed, keyType, wsAddress, outFile, did }) => {
         await connect(wsAddress)