Instagram typing indicator support + diagnosable startTyping - #8
Merged
Conversation
Server-side Instagram support ships in the Zernio API; this updates the stale "no-op on Instagram" docs, surfaces the endpoint's success boolean from sendTyping, and debug-logs startTyping failures instead of swallowing them silently. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Fixes #7. The typing indicator was a server-side no-op on Instagram; server support ships in zernio-dev/Schedule-Posts-API#1966. Separately,
startTypingswallowed every error silently, so integrators could not tell a genuine failure from an unsupported platform.What
sendTypingnow returnsPromise<boolean>: the endpoint'ssuccessflag (the API returns 200 even when the platform call fails; the boolean reports whether an indicator was actually sent). Void callers are unaffected.startTypingstays best-effort but logs at debug level (existingLoggermechanism) both on thrown errors and onsuccess: false, instead of a silent catch.sendTypingerror propagation (102 passing).coverage/added to.gitignore.Follow-ups
package-lock.jsonis out of sync with the v0.4.0 release commit (version still 0.2.3); left out of this PR, worth a separate chore commit.🤖 Generated with Claude Code