8000 Feature: Include contact names in JSON message export · Issue #50 · tbvdm/sigtop · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Feature: Include contact names in JSON message export #50

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 acco 8000 unt related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
ayancey opened this issue Aug 13, 2024 · 3 comments
Open

Feature: Include contact names in JSON message export #50

ayancey opened this issue Aug 13, 2024 · 3 comments

Comments

@ayancey
Copy link
ayancey commented Aug 13, 2024

When you run sigtop export-messages, it returns the sender's display name if the format is text or text-short. Because json output returns directly from the database, there's no display name included.

An option like json-names might be nice which joins sourceServiceId from messages table to serviceId in the conversations table.

Thanks!
@tbvdm
Copy link
Owner
tbvdm commented Aug 20, 2024

Good point. Another possibility is to export the json column from the conversations table into a separate conversations.json file. Would that work for you?

@ayancey
Copy link
Author
ayancey commented Aug 21, 2024

Good point. Another possibility is to export the json column from the conversations table into a separate conversations.json file. Would that work for you?

That's a good idea. I'll take a whack at a PR, but I know next to nothing about Go. 😅

@aloisdg
Copy link
aloisdg commented Oct 19, 2024 •
edited
Loading

@ayancey any update on the whack PR? I am not a Go dev either but I am willing to help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@aloisdg @ayancey @tbvdm
0