Ability to take screenshot of particular chats
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
Research direction
Start by reading the screenshot endpoint and how it identifies chats and messages; the issue does not name files or tests. Then check how each WhatsApp engine handles screenshots and message positioning. Done means the endpoint can capture a requested chat, ideally scrolled to a message ID, so the latest messages can be used as proof.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe. I'm always
frustrated when a client says that WhatsApp didn't send a message, while our logs say it got sent.
We are 100% sure the message is sent; we have the ids, and confirmations, but for the client this is not enough; these are just "numbers that prove nothing".
Sometimes we are able to find the message sent on the most recent screenshot, but if days have passed, no way.
Describe the solution you'd like
Improvements to the screenshot endpoint, where I can send a chat ID and get a screenshot of this chat, even though it will not show all the messages sent, but in most cases the last messages displayed in the chat are enough.
If we can scroll to the message id before take the screenshot, even better.
Describe alternatives you've considered
I didn't find any alternative, but my goal is to have an screenshot right after a message is sent, and save it as a proof.
Additional context Add any other context or screenshots about the feature
request here.
- Dominant language
- TypeScript
- Stars
- 7.6k
- Forks
- 1.8k
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 7
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from devlikeapro/waha
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
devlikeapro/waha#2322 ·
Maintainers usually reply within 2 days
-
patron:PLUS
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
devlikeapro/waha#2167 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
devlikeapro/waha#2324 ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
devlikeapro/waha#2321 ·
Maintainers usually reply within 2 days
-
GOWS: FAILED has no reason, and temporary ban / stream replaced / client outdated leave the session silently deadPossibly taken @diego-goncalves-teixeira claimed this 5 days ago. Openpatron:PLUS
Difficulty 4/5 3-5 days Newbie friendliness 25/100
devlikeapro/waha#2317 ·
Maintainers usually reply within 2 days
All issues in devlikeapro/waha
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
kunchenguid/gh-axi#220 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
prerender: wait for env-runner worker readiness before crawlingPossibly taken @sarankumar1325 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day