Skip to content

feat(push): get_push_devices and get_push_device, sync and async - #14

Merged
Domantas merged 3 commits into
mainfrom
audit/push
Sep 27, 2026
Merged

Domantas merged 3 commits into
mainfrom
audit/push

Conversation

@Domantas

Copy link
Copy Markdown
Contributor

What changes

  • Push device reads: get_push_devices (filter by userId, deviceKey or platform — a page is a page of users, follow hasMore) and get_push_device(id), on the sync and the async client. Routes 37 → 39.
  • Push tests assert every field the gateway reads for the 5 campaign targets and the 8 providers; docs for the device reads.
  • Not behind main; no type files in this SDK (requests are dicts).

Tests

pytest 615 passed (push: 60).

Merging

Please use Squash and merge, so semantic-release reads this title as the one commit: the branch's own commits are titled item: … / test(push) and would not publish on their own.

🤖 Generated with Claude Code

Domantas and others added 3 commits September 22, 2026 11:47
… field names

Squash of audit/push-sdk-go-js-py (campaign item sdk-go-js-py).

The body-variant tests only proved that a body reached the wire unchanged, so a
wrong value still passed. They now send and assert every field the gateway
actually reads for each variant, and a guard test fails if a target or provider
is not one the gateway accepts. A device-register body test was added, and
docs/hub/push.md lists the own fields per provider and per target.

This caught a real defect: the Chrome-extension provider was tested and
documented as CodeMashChromePlugin. That string parses as a PushProvider, but
the gateway save converter (Hub.Push/Integrations/Save_.cs:94-121) has no arm
for it and answers "Unsupported provider". The value is ChromePush. Anyone
following the old docs could not save a Chrome-extension integration.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@Domantas
Domantas merged commit 4fd1b6c into main Sep 27, 2026
8 checks passed
@Domantas
Domantas deleted the audit/push branch September 27, 2026 04:59
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