maxObjectBytes property

  1. @override
int? get maxObjectBytes
override

The largest a single path in a TomChangeset may be, or null when the backend imposes no limit of its own.

This exists because of the ordering it fixes, not because a number is interesting. An application that lets a user embed image bytes needs to know this before the bytes are in a document: a backend that refuses those bytes refuses them at save time — after the paste was accepted, the block inserted and the editing done. Asking the backend first turns that into a refusal at ingest, which is the only point at which the user has lost nothing.

It is deliberately a limit on one object, not on a save: measurement against real GitHub found the ceiling is per blob and that a single commit carrying 96 MiB across twelve blobs lands fine, so "one save = one atomic commit" survives an asset-bearing document unchanged. A backend that ever needed a whole-save budget would be giving up that invariant, and that is a spec decision, not a field.

Implementation

@override
int? get maxObjectBytes => maxBlobBytes;