mirror of
https://github.com/penpot/penpot.git
synced 2026-11-09 19:41:34 +00:00
c05a05b4c3
The job-def freezes the export items the frontend prepares (file, page, object, type, scale, name and the optional share-id) and routes the job to the `:exporter` queue through the new `::jobs/queue-name` metadata, which the creation command reads and the substrate never does. The handler only raises: the work runs on the external worker, and a wrong configuration that claimed the job on a JVM runner fails visibly. Export has one command per job type: `create-export-binfile-job` keeps the exact behavior the export command had, and `create-export-assets-job` checks the read permission of every file named in the items before anything is stored. The family quote still counts every export job of either kind. AI-assisted-by: glm-5.3-flash