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.

Sign up for GitHub

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

Jump to bottom

SAYFROM / SAYEX should enter chat history properly #312

Closed
silentwings opened this issue Feb 11, 2019 · 4 comments
Closed

SAYFROM / SAYEX should enter chat history properly #312

silentwings opened this issue Feb 11, 2019 · 4 comments
Labels
bug db field change

Comments

@silentwings
Copy link
Contributor

No description provided.

@silentwings silentwings self-assigned this Feb 11, 2019
silentwings added a commit that referenced this issue Feb 24, 2019
@silentwings
workaround for #312
e87f70c
@silentwings silentwings removed their assignment Feb 24, 2019
@silentwings
Copy link
Contributor Author

should fix this properly when #183 is done

@silentwings silentwings changed the title SAIDFROM should enter chat history SAIDFROM / SAYEX should enter chat history properly Mar 1, 2019
@silentwings
Copy link
Contributor Author

needs two new db fields:
bridged_id (int or nil)
ex_message (bool)

@silentwings silentwings mentioned this issue Mar 31, 2019
Closed
@silentwings
Copy link
Contributor Author

there is now a boolean "ex_msg" that comes in the json SAID commands sent in response to GETCHANNELHISTORY

@silentwings silentwings changed the title SAIDFROM / SAYEX should enter chat history properly SAYFROM / SAYEX should enter chat history properly Feb 19, 2020
silentwings added a commit that referenced this issue Feb 19, 2020
@silentwings
fix #312, SAYFROM part
11a8ed1
@silentwings silentwings mentioned this issue Feb 19, 2020
Merged
@silentwings
Copy link
Contributor Author

silentwings commented Feb 26, 2020 •
edited
Loading

reopened so that the pr can close it when merged

@silentwings silentwings reopened this Feb 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug db field change
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@silentwings