fileBinary not present in TS definitions for filesDownload

[unilynx]

Describe the bug
Property 'fileBinary' does not exist on type 'FileMetadata'.

To Reproduce

import { Dropbox } from "dropbox";
const dbx = new Dropbox({ accessToken: '...' });
const fileinfo = await dbx.filesDownload({ path: '...' });
console.log(fileinfo.result.fileBinary);

This will give the aforementioned TypeScript error, although fileBinary does actually exist if you console.log the object:

DropboxResponse {
  status: 200,
  ...,
  result: {
    name: 'Mambo Kurt - Paradise City.mp3',
    path_lower: '/mambo kurt - paradise city.mp3',
    path_display: '/Mambo Kurt - Paradise City.mp3',
    id: 'id:cVRCL-ln7TwAAAAAAAAABg',
    client_modified: '2024-04-02T12:00:42Z',
    server_modified: '2024-04-02T12:00:42Z',
    rev: '6151bdaff690d91f858d3',
    size: 1425936,
    is_downloadable: true,
    content_hash: '5d6fd78d1255d1072341a7c51552b3fc430a5f17e4d00eff6f15c249aa25d44c',
    fileBinary: <Buffer ff fb 90 6c 00 0f f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ... 1425886 more bytes>
  }
}

Expected Behavior
I'd expect no compilation errors

I would expect fileBinary: Buffer in the FileMetadata type, or something like fileBlob?

(Issue #809 might be related but is looking for a fileBlob, not a fileBinary)

Actual Behavior
Compilation fails.

Versions

• What version of the SDK are you using?
  10.34.0

• What version of the language are you using?
  Node 20

• Are you using Javascript or Typescript?
  TypeScript

[greg-db]

Thanks for the report! I'll ask the team to fix that up.

[binajmen]

No offense but I'm starting to doubt things will change.

1. It was already reported 7 years ago: https://www.dropboxforum.com/discussions/101000014/javascript-api-clarity---filesdownload/282827
2. I created a simple PR about another type issue that was never merged after 3 weeks: Update index.d.ts #1146
3. This repository last commit is from 2 years ago.

I guess my question is: should I write my own javascript wrapper instead? You can be honest :)

[alyx-db]

@binajmen

Thank you for sharing your concerns. We understand how frustrating it can be when an issue persists for an extended period.

While I cannot provide a timeline regarding a resolution, I can assure you that your feedback has been recorded and have noted this concern with our team. In the meantime, creating your own "wrapper" is a valid approach to address your specific needs and maintain functionality within your integration.

[binajmen]

I can assure you that your feedback has been recorded and have noted this concern with our team

Seven years, three months, and counting, yet your 'recording feedback' clearly means filing it into the void. At this rate, we'll colonise Mars before this simple issue gets fixed. Thanks for confirming that 'noting concerns with the team' translates to 'absolutely nothing will happen' in Dropbox language.

[alyx-db]

@binajmen,

We hear your frustration, and we want you to know your feedback hasn’t gone unnoticed. While we can’t always act on every issue immediately, we’ve made sure your feedback has been seen by the relevant team.