MT list - when dropbox remote backup directory doesnt exist

[boly38]

( following close subject #98 )

What if end-user having featured dropbox wants to list backups for a backup directory which doesn't exists on Dropbox side ?

• actual: this returns an error (ex. Error: Dropbox path '/backup/myBackups' dont exist )
• maybe we expect to simply return an empty result..

In fact, the action to create a new backup will create the remote backup directory when missing, so there is no reason to reject a list having a missing remote backup directory

[boly38]

how to reproduce

• set DBX context

# TIP: get key,secret from dropbox developers app dev portal : https://www.dropbox.com/developers/apps/
❯ export MT_DROPBOX_APP_KEY=
❯ export MT_DROPBOX_APP_SECRET=
# TIP: long-lived offline refresh-token. cf. https://github.com/boly38/dropbox-refresh-token
❯ export MT_DROPBOX_REFRESH_TOKEN=

• list backup for an unknown directory

❯ export MT_PATH=backup/myBackup
❯ export MT_DROPBOX_DEBUG=true
❯ node mt list
isValid:false error:invalid_access_token/ - so dropboxRefreshAccessToken
Dropbox filesListFolder /backup/myBackup:
filesListError DropboxResponseError: Response failed with a 409 code
    at /mnt/c/WORK/perso/node-mongotools/node_modules/.pnpm/dropbox@10.34.0_@types+node-fetch@2.6.13/node_modules/dropbox/cjs/src/response.js:34:11
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  status: 409,
  headers: Headers {
    [Symbol(map)]: [Object: null prototype] {
      'content-type': [Array],
      'cache-control': [Array],
      'content-security-policy': [Array],
      'x-content-type-options': [Array],
      date: [Array],
      server: [Array],
      'content-length': [Array],
      'x-dropbox-response-origin': [Array],
      'x-dropbox-request-id': [Array]
    }
  },
  error: {
    error_summary: 'path/not_found/..',
    error: { '.tag': 'path', path: [Object] }
  }
}
Error "Dropbox path '/backup/myBackup' dont exist"
❯ ll ./backup/myBackup/
total 0

with #98 local backup dir is now created, but while querying dropbox we get a 409 (conflict 🤔 ) with an error_summary: 'path/not_found/..'