[Feature] Add fileSizeInByte to top-level AssetResponseDto

[Lemonnik6484]

I have searched the existing feature requests, both open and closed, to make sure this is not a duplicate request.

• Yes

The feature

Related to #31694, but instead of a new bulk endpoint, the fix is to expose fileSizeInByte at the top level of the response. Currently fileSizeInByte only lives inside exifInfo, so clients must request withExif: true just to get file sizes for directory listings. This forces downloading the full EXIF payload even when only filename + size are needed. For albums with thousands of assets, this makes paginated loads extremely slow

Adding fileSizeInByte as a top-level field would let withExif: false still return meaningful file sizes, significantly reducing API response size for listing operations

Platform

• Server
• Web
• Mobile

[bo0tzz]

For albums with thousands of assets, this makes paginated loads extremely slow

And adding more fields to the top level response would start slowing down everything that doesn't need them.

[Lemonnik6484]

Then what about a flag that would specifically add that field to the top level?

[bo0tzz]

No, that's all way too specific, we won't be doing anything like that.
Fwiw I tested with the demo instance and can't find the "extremely slow" pagination you mention. You might want to check that your database has all its indices, and is on proper fast storage and such.