ConstReadonlyignoreMinorErrors: booleanReadonlystruct: 0 | 1 | 2 | "undef"How should ExifTool handle nested structures?
0 = Read/copy flattened tags1 = Read/copy structures2 = Read/copy both flattened and structured tags, but flag flattened
tags as "unsafe" for copying"undef" = Same as 0 for reading and 2 for copyingReadonlywriteArgs: string[]Any additional arguments that should be added by default to all write
tasks, like ["-overwrite_original"]. The value provided to the ExifTool
constructor can be overridden in the call to ExifTool.write.
Security: entries are passed through to the underlying exiftool
process verbatim. Never pass attacker-controlled strings here. The
library rejects any entry containing \r, \n, or \0 as a
defense-in-depth measure, but provides no other sanitization.
Should we ignore minor errors when reading metadata?