Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 16 additions & 9 deletions docs.json
Original file line number Diff line number Diff line change
Expand Up @@ -216,7 +216,6 @@
"group": "Supabase",
"pages": [
"integration-guides/supabase-+-powersync",
"integration-guides/supabase-+-powersync/handling-attachments",
"integration-guides/supabase-+-powersync/realtime-streaming",
"integration-guides/supabase-+-powersync/rls-and-sync-rules",
"integration-guides/supabase-+-powersync/local-development"
Expand Down Expand Up @@ -424,14 +423,6 @@
"tutorials/client/sdks/web/next-js"
]
},
{
"group": "Attachments / Files",
"pages": [
"tutorials/client/attachments-and-files/overview",
"tutorials/client/attachments-and-files/aws-s3-storage-adapter",
"tutorials/client/attachments-and-files/pdf-attachment"
]
},
{
"group": "Performance",
"pages": [
Expand Down Expand Up @@ -693,6 +684,22 @@
{
"source": "/client-sdk-references/kotlin-multiplatform/libraries/room",
"destination": "/client-sdk-references/kotlin/libraries/room"
},
{
"source": "/tutorials/client/attachments-and-files/overview",
"destination": "/usage/use-case-examples/attachments-files"
},
{
"source": "/tutorials/client/attachments-and-files/aws-s3-storage-adapter",
"destination": "/usage/use-case-examples/attachments-files"
},
{
"source": "/tutorials/client/attachments-and-files/pdf-attachment",
"destination": "/usage/use-case-examples/attachments-files"
},
{
"source": "/integration-guides/supabase-+-powersync/handling-attachments",
"destination": "/usage/use-case-examples/attachments-files"
}
]
}
Binary file added images/attachments/attachments-flow.png
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Item 11 in this diagram is in a slightly confusing position. Maybe this diagram could use another arrow from the local file storage block back to the Attachment Queue?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That might imply that the local storage has anything to do with altering the state. but it's only the Attachment Queue that can alter that state. I can't think of a balanced way to do this tbh.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't have a strong opinion on this. When I was first looking at this diagram, I was (in my mind) viewing this more as a process diagram than a state diagram.

Copy link
Contributor

@Chriztiaan Chriztiaan Jan 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The numbers and arrows describing different flows/orders is very confusing. Would it be clearer if the download and upload flows were separate diagrams? Or:
Main diagram shows just the user-visible flow: save -> upload -> sync -> download -> stored
Separate section explains the technical mechanism: "How the queue system works", "Data model updates", etc.


Either way, open to alternatives. I just found this non-trivial to follow.

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading