Rename "channels" to "conversations."

The term "channel" for a conversational container has a long and storied history, but is mostly evocative of IRC and of other, ah, "nerd-centric" services. It does show up in more widespread contexts: Discord and Slack both refer to their primary conversational containers as "channels," for example. However, I think it's unnecessary jargon, and I'd like to do away with it.

To that end, this change pervasively changes one term to the other wherever it appears, with the following exceptions:

* A `channel` concept (unrelated to conversations) is also provided by an external library; we can't and shouldn't try to rename that.
* The code to deal with the `pilcrow:channelData` and `pilcrow:lastActiveChannel` local storage properties is still present, to migrate existing data to new keys. It will be removed in a later change.

This is a **breaking API change**. As we are not yet managing any API compatibility promises, this is formally not an issue, but it is something to be aware of practically. The major API changes are:

* Paths beginning with `/api/channels` are now under `/api/conversations`, without other modifications.
* Fields labelled with `channel…` terms are now labelled with `conversation…` terms. For example, a `message` `sent` event is now sent to a `conversation`, not a `channel`.

This is also a **breaking UI change**. Specifically, any saved paths for `/ch/CHANNELID` will now lead to a 404. The corresponding paths are `/c/CONVERSATIONID`. While I've made an effort to migrate the location of stored data, I have not tried to provide adapters to fix this specific issue, because the disruption is short-lived and very easily addressed by opening a channel in the client UI.

This change is obnoxiously large and difficult to review, for which I apologize. If this shows up in `git annotate`, please forgive me. These kinds of renamings are hard to carry out without a major disruption, especially when the concept ("channel" in this case) is used so pervasively throughout the system.

I think it's worth making this change that pervasively so that we don't have an indefinitely-long tail of "well, it's a conversation in the docs, but the table is called `channel` for historical reasons" type issues.

Merges conversations-not-channels into main.

1 files changed, 184 insertions, 0 deletions

diff --git a/src/conversation/handlers/delete/test.rs b/src/conversation/handlers/delete/test.rs
new file mode 100644
index 0000000..2718d3b
--- /dev/null
+++ b/src/conversation/handlers/delete/test.rs
@@ -0,0 +1,184 @@
+use axum::extract::{Path, State};
+use itertools::Itertools;
+
+use crate::{conversation::app, test::fixtures};
+
+#[tokio::test]
+pub async fn valid_conversation() {
+    // Set up the environment
+
+    let app = fixtures::scratch_app().await;
+    let conversation = fixtures::conversation::create(&app, &fixtures::now()).await;
+
+    // Send the request
+
+    let deleter = fixtures::identity::create(&app, &fixtures::now()).await;
+    let response = super::handler(
+        State(app.clone()),
+        Path(conversation.id.clone()),
+        fixtures::now(),
+        deleter,
+    )
+    .await
+    .expect("deleting a valid conversation succeeds");
+
+    // Verify the response
+
+    assert_eq!(conversation.id, response.id);
+
+    // Verify the semantics
+
+    let snapshot = app.boot().snapshot().await.expect("boot always succeeds");
+    let created = snapshot
+        .events
+        .into_iter()
+        .filter_map(fixtures::event::conversation)
+        .filter_map(fixtures::event::conversation::created)
+        .exactly_one()
+        .expect("only one conversation has been created");
+    // We don't expect `conversation` to match the event exactly, as the name will have
+    // been tombstoned and the conversation given a `deleted_at` date.
+    assert_eq!(conversation.id, created.conversation.id);
+}
+
+#[tokio::test]
+pub async fn invalid_conversation_id() {
+    // Set up the environment
+
+    let app = fixtures::scratch_app().await;
+
+    // Send the request
+
+    let deleter = fixtures::identity::create(&app, &fixtures::now()).await;
+    let conversation = fixtures::conversation::fictitious();
+    let super::Error(error) = super::handler(
+        State(app.clone()),
+        Path(conversation.clone()),
+        fixtures::now(),
+        deleter,
+    )
+    .await
+    .expect_err("deleting a nonexistent conversation fails");
+
+    // Verify the response
+
+    assert!(matches!(error, app::DeleteError::NotFound(id) if id == conversation));
+}
+
+#[tokio::test]
+pub async fn conversation_deleted() {
+    // Set up the environment
+
+    let app = fixtures::scratch_app().await;
+    let conversation = fixtures::conversation::create(&app, &fixtures::now()).await;
+
+    app.conversations()
+        .delete(&conversation.id, &fixtures::now())
+        .await
+        .expect("deleting a recently-created conversation succeeds");
+
+    // Send the request
+
+    let deleter = fixtures::identity::create(&app, &fixtures::now()).await;
+    let super::Error(error) = super::handler(
+        State(app.clone()),
+        Path(conversation.id.clone()),
+        fixtures::now(),
+        deleter,
+    )
+    .await
+    .expect_err("deleting a deleted conversation fails");
+
+    // Verify the response
+
+    assert!(matches!(error, app::DeleteError::Deleted(id) if id == conversation.id));
+}
+
+#[tokio::test]
+pub async fn conversation_expired() {
+    // Set up the environment
+
+    let app = fixtures::scratch_app().await;
+    let conversation = fixtures::conversation::create(&app, &fixtures::ancient()).await;
+
+    app.conversations()
+        .expire(&fixtures::now())
+        .await
+        .expect("expiring conversations always succeeds");
+
+    // Send the request
+
+    let deleter = fixtures::identity::create(&app, &fixtures::now()).await;
+    let super::Error(error) = super::handler(
+        State(app.clone()),
+        Path(conversation.id.clone()),
+        fixtures::now(),
+        deleter,
+    )
+    .await
+    .expect_err("deleting an expired conversation fails");
+
+    // Verify the response
+
+    assert!(matches!(error, app::DeleteError::Deleted(id) if id == conversation.id));
+}
+
+#[tokio::test]
+pub async fn conversation_purged() {
+    // Set up the environment
+
+    let app = fixtures::scratch_app().await;
+    let conversation = fixtures::conversation::create(&app, &fixtures::ancient()).await;
+
+    app.conversations()
+        .expire(&fixtures::old())
+        .await
+        .expect("expiring conversations always succeeds");
+
+    app.conversations()
+        .purge(&fixtures::now())
+        .await
+        .expect("purging conversations always succeeds");
+
+    // Send the request
+
+    let deleter = fixtures::identity::create(&app, &fixtures::now()).await;
+    let super::Error(error) = super::handler(
+        State(app.clone()),
+        Path(conversation.id.clone()),
+        fixtures::now(),
+        deleter,
+    )
+    .await
+    .expect_err("deleting a purged conversation fails");
+
+    // Verify the response
+
+    assert!(matches!(error, app::DeleteError::NotFound(id) if id == conversation.id));
+}
+
+#[tokio::test]
+pub async fn conversation_not_empty() {
+    // Set up the environment
+
+    let app = fixtures::scratch_app().await;
+    let conversation = fixtures::conversation::create(&app, &fixtures::now()).await;
+    let sender = fixtures::user::create(&app, &fixtures::now()).await;
+    fixtures::message::send(&app, &conversation, &sender, &fixtures::now()).await;
+
+    // Send the request
+
+    let deleter = fixtures::identity::create(&app, &fixtures::now()).await;
+    let super::Error(error) = super::handler(
+        State(app.clone()),
+        Path(conversation.id.clone()),
+        fixtures::now(),
+        deleter,
+    )
+    .await
+    .expect_err("deleting a conversation with messages fails");
+
+    // Verify the response
+
+    assert!(matches!(error, app::DeleteError::NotEmpty(id) if id == conversation.id));
+}