{"version":"2.1.251","anchor":"pdf-reads-now-report-the-file-path-they-came-from","canonical_anchor":"pdf-reads-now-report-the-file-path-they-came-from","heading":"PDF reads now report the file path they came from","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/pdf-reads-now-report-the-file-path-they-came-from","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### PDF reads now report the file path they came from\n\nPDF read results now include the file path they came from.\n\n**What**\n\nReading a PDF, or a single page from one, now includes the file path in the result alongside the extracted content. Notebook and PDF reads also go through a shared file-handle layer rather than passing raw paths around.\n\n**Details**\n\n- Applies to both whole-PDF reads and page-level extraction, which previously returned the content without saying which file it came from.\n- Unconditional; no setting involved.\n\n**Evidence**\n\n`file: { ...mn.file, filePath: o }`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}