Skip to content

Commit 4be4480

Browse files
Consider inline field while creating SSOR attachment object (#50)
## Summary <!-- Provide a brief description of the story behind this PR, as if explaining to a non-technical person. Or to an LLM so it can learn from it for future (autonomous) code improvements. Feel free to point to a deeper design doc, if applicable. --> This PR fixes that `inline` field is passed from attachment metadata object to ssor attachment one. Loader needs this while loading inline attachments for articles. ## Connected Issues <!-- Have you cared to connect this PR to a work item in DevRev, so that we can understand future routing and attribution? --> - https://app.devrev.ai/devrev/works/ISS-196132
1 parent 0246e05 commit 4be4480

File tree

2 files changed

+5
-0
lines changed

2 files changed

+5
-0
lines changed

src/uploader/uploader.interfaces.ts

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -79,6 +79,7 @@ export interface SsorAttachment {
7979
actor_id?: {
8080
external: string;
8181
};
82+
inline?: boolean;
8283
}
8384

8485
export interface StatsFileResponse {

src/workers/worker-adapter.ts

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -740,6 +740,10 @@ export class WorkerAdapter<ConnectorState> {
740740
};
741741
}
742742

743+
if (attachment.inline) {
744+
ssorAttachment.inline = true;
745+
}
746+
743747
await this.getRepo('ssor_attachment')?.push([ssorAttachment]);
744748
}
745749
return;

0 commit comments

Comments
 (0)