Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix forwarding messages from encrypted to unencrypted chat without creating a new message object #5125

Merged
merged 6 commits into from
Jan 17, 2024

Commits on Jan 16, 2024

  1. Configuration menu
    Copy the full SHA
    ab3d19e View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    8da0bed View commit details
    Browse the repository at this point in the history
  3. test: Bring test_forward_encrypted_to_unencrypted into line with curr…

    …ent API
    
    Currently `Chat.send_msg()` modifies the source message and returns another message object
    equivalent to the source one. That's how it works in the core and thus in Python bindings too.
    iequidoo committed Jan 16, 2024
    Configuration menu
    Copy the full SHA
    fe005f8 View commit details
    Browse the repository at this point in the history
  4. fix: chat::send_msg: Remove encryption-related params from already se…

    …nt message
    
    This allows to send existing messages (incoming and outgoing) taken from encrypted chats, to
    unencrypted ones. `Param::ForcePlaintext` is removed as well -- if a message can be sent encrypted
    this time, nothing bad with this.
    iequidoo committed Jan 16, 2024
    Configuration menu
    Copy the full SHA
    e2e8a8d View commit details
    Browse the repository at this point in the history
  5. Configuration menu
    Copy the full SHA
    a062a8f View commit details
    Browse the repository at this point in the history

Commits on Jan 17, 2024

  1. Configuration menu
    Copy the full SHA
    a6255c0 View commit details
    Browse the repository at this point in the history