Drafts keep their subscribers when an update doesn't address them

[jeremy]

Updating a drafted document, message, schedule entry, cloud file, or Google document without sending subscriptions or notify used to unsubscribe everyone — the subscriber list collapsed to the creator (plus the updater, on the two endpoints that add them). The sparse "Update a document" example in these very docs triggered it.

Now omission preserves the list, and sending either subscriptions or notify still recomputes it.

Each section states the guarantee its own endpoint makes, which is not uniform:

• Documents and messages keep the creator and whoever makes the update on the list.
• Cloud files, Google documents and schedule entries keep the creator only.

Two further notes:

• Messages — on update, omitting subscriptions now preserves rather than re-subscribing the whole project. Creation is unchanged: omitting subscriptions still notifies and subscribes everyone on the project.
• Schedule entries — participants address subscribers too, since a drafted entry's subscribers are derived from its participants. A draft keeps its current subscribers only when the request omits subscriptions, notify and the participant parameters; sending any of them recomputes, which is what unsubscribes someone dropped from the entry.

Source: basecamp/bc3#12494.

---

Synced from bc3 doc/api/ by script/api/sync_to_bc3_api — not a hand-edit.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.