Skip to content

docs: say what a Reply before the LinkedIn scheduler does with --schedule-id - #35

Merged
ArtemKosolap merged 1 commit into
mainfrom
REPLY-53111-docs-linkedin-scheduler
Oct 31, 2026
Merged

ArtemKosolap merged 1 commit into
mainfrom
REPLY-53111-docs-linkedin-scheduler

Conversation

@ArtemKosolap

Copy link
Copy Markdown
Contributor

What

The help of the four LinkedIn sends (contact linkedin-connect, linkedin-message, linkedin-inmail, linkedin-voice) and the README's direct-send flags paragraph now say what a Reply without the LinkedIn scheduler does with the schedule's flags:

A Reply that knows direct sends but not yet the LinkedIn scheduler answers --schedule-id or --use-contact-time-zone on a LinkedIn send with errors[] naming the field (reply.invalid_request), and one that knows neither sends at once, as without them.

The test comment that described the older behaviour is corrected to match. No code path changes.

Why

Reply's API can reach direct sends before it reaches the LinkedIn scheduler. Such a Reply refuses scheduleId or useContactTimeZone on a LinkedIn send with a 400 whose errors[] names the field, which the CLI already reports as reply.invalid_request. The help and README described only a Reply that knows neither feature: it ignores the fields and sends at once. A caller who meets the 400 should find it explained where they look, and know that the send was not made.

Verification

  • commands.test.ts asserts the sentence in the help of each LinkedIn send and its absence from contact send-email's help. The assertion was seen failing before the help text changed.
  • npm run build (tsc): clean.
  • npm test (vitest): 60 files, 942 passed, 5 skipped, 0 failed.
  • The repository has no lint script; commitlint ran on the commit through the husky hook.

Release

A docs: commit, so semantic-release publishes no release.

…dule-id

A Reply that has direct sends but not yet the LinkedIn scheduler answers scheduleId or
useContactTimeZone on a LinkedIn send with a 400 whose errors[] names the field, which the CLI
reports as reply.invalid_request; one that has neither sends at once. The LinkedIn sends' help
and the README now say both.
@ArtemKosolap
ArtemKosolap merged commit 6fbd414 into main Oct 31, 2026
6 checks passed
@ArtemKosolap
ArtemKosolap deleted the REPLY-53111-docs-linkedin-scheduler branch October 31, 2026 14:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant