Add server-side identify and person property update helpers
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
Research direction
Start with the public_api.snapshot, existing capture/3 and feature flag APIs, then compare the sdk-specs identify specification. Define the public server-side identify behavior, including optional $set_once and standard event options, and add tests plus public API documentation or snapshot updates. Done means the helpers use the existing capture/batching path and their behavior is covered by tests.
Written by the indexing model from the issue text.
Description
Summary
Add server-side public helpers for identifying users and updating person properties.
Why
sdk-specs marks identify as applicable to both client and server SDKs. Server SDKs should be able to emit stateless person profile updates without relying on callers to hand-build $identify, $set, or $set_once capture events.
Current status
public_api.snapshot exposes capture/3 and feature flag APIs, but no public identify, set, or set_once helpers.
Suggested scope
- Add an idiomatic Elixir API for server-side
identifythat emits$identifywith$setand optional$set_once. - Consider separate
set/set_oncehelpers if that matches backend SDK parity better. - Support standard event options where possible: timestamp, uuid, and disable_geoip.
- Route through the same capture/batching path and future
before_sendhook. - Add tests and update public API docs/snapshot.
References
- Dominant language
- Elixir
- Stars
- 66
- Forks
- 33
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 21
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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 PostHog/posthog-elixir
-
enhancement feature/feature-flags
Difficulty 4/5 3-5 days Newbie friendliness 45/100
PostHog/posthog-elixir#215 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
PostHog/posthog-elixir#209 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 55/100
PostHog/posthog-elixir#149 ·
Maintainers usually reply within 1 day
-
bug enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
PostHog/posthog-elixir#147 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
PostHog/posthog-elixir#146 ·
Maintainers usually reply within 1 day
All issues in PostHog/posthog-elixir
Similar issues
-
@swmansion/popcorn: published .d.ts files lack extensions on relative imports, breaking moduleResolution node16/nodenextPossibly taken @Huyvux12 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
software-mansion/popcorn#929 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
ash-project/ash#3127 ·
Maintainers usually reply within 1 day
-
Bug: Table layout and date column are cut off on mobile screens on the Tournaments -> History pageOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
hexlet-codebattle/codebattle#2375 ·
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
wintermeyer/vutuv#2388 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100