Artifact database writes can take a local JSON file, so big documents skip the conversation.
What's wrong with this entry?
Artifact database writes accept file_path pointing at a local JSON file whose top-level object becomes the document, so a large document no longer has to pass through the conversation. Exactly one of inline data or file_path is required; giving both or neither is a validation error.
- The file is read under the normal Read permission rules, parsed as JSON, and must be a top-level object; failures are reported as read denied, file not found, invalid JSON, not an object, or too large.
- Swapping between inline data and a file after approval is refused and forces a fresh permission check.
- The write approval no longer blanket-covers files that need their own Read approval.
file_path does not hold valid JSON \u2014 write_db sends the file's JSON object as the document, saved as local JSON files (the destination follows the file-edit rules), a local JSON file whose top-level object is sent as the document
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.239
Backslashes in filenames are left alone on macOS and Linux
Both mention file path
-
v2.1.235
Remote settings can be primed from local storage instead of probing disk
Both mention path
-
v2.1.239
File uploads report why they failed and stop retrying forever
Both mention file