Skip to content

feat: replace chat-cli /connect with /dm and /new - #206

Open
mchenani wants to merge 1 commit into
mch/libchat-refactoring-accountfrom
mch/libchat-refactoring-connect
Open

feat: replace chat-cli /connect with /dm and /new#206
mchenani wants to merge 1 commit into
mch/libchat-refactoring-accountfrom
mch/libchat-refactoring-connect

Conversation

@mchenani

Copy link
Copy Markdown
Contributor

No description provided.

@jazzz jazzz left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

All these changes make sense to me. No blockers but a few notes.

Note: For reviews I tend to use this feedback ladder so there is no ambiguity about severity or importance -https://www.netlify.com/blog/2020/03/05/feedback-ladders-how-we-encode-code-reviews-at-netlify/

Comment thread bin/chat-cli/src/app.rs
Comment on lines +23 to +24
/// Which kind of MLS conversation this is. `Dm` is a DirectV1 1:1 — no members
/// can be added; `Group` is an addable GroupV2 conversation.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

[Dust] The Actual ConversationType being used will change overtime. Listing them explicitly will result in the docs becoming out of date quickly. Consider removing.

Comment thread bin/chat-cli/src/app.rs
Comment on lines +25 to +29
#[derive(Debug, Clone, Copy, PartialEq, Eq, Serialize, Deserialize)]
pub enum ChatKind {
Dm,
Group,
}

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

[!] There was a previous "ConvoClass" structure but I'm realizing it never landed in generic_client. We should eventually think about exposing this information so it is available for all clients.

Comment thread bin/chat-cli/src/app.rs
Comment on lines -245 to +284
self.add_system_message("/connect <address> - Connect using an address");
self.add_system_message("/dm <address> - Start a direct (1:1) chat");

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

[Sand] This PR is tightly coupled with #205 . Short PR's are great, however its hard to see how these changes will all land together. Particularly with some unrelated lines being deleted in this PR.

In the future I don't have any issue reviewing tightly coupled items together in a single PR. Especially if the commits are clean.

Comment thread bin/chat-cli/src/app.rs
Comment on lines +323 to +325
// First token is the (optional) group name; any remaining tokens
// are addresses to invite at creation. `/new` alone makes an empty
// group.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

[?] Is there a functional reason to not force developers to create groups with a defined name?

Comment thread bin/chat-cli/README.md

**Direct message (1:1):**

1. Alice types `/account` and sends Bob her address.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

[!] There is a proposal to remove Alice and Bob from chat level documentation : https://github.com/logos-co/logos-lips/blob/master/docs/messaging/informational/raw/chat-cast.md -- Feedback welcome

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants