Repository navigation
docs: sort the 1.0.0 migration guide, and add the facts from the retired posthog.com Rust page - #362
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
PostHog Review · Standard · reviewed fbd7ac3: 1 Should fix.
See this review and its findings in PostHog Review. Comment @posthog review --deep for a Deep review. A Deep review takes longer and looks deeper than a Standard review.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit ceaf19c)
The posthog.com Rust SDK page redirects to this reference once 1.0.0 ships, so its setup, how-to, and feature flag sections now live in docs/getting-started.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit 7776e30)
This reverts commit b15476c.
…her page has Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The reference renders each doc comment under its entry, per major, so facts about one API belong there. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
dustinbyrne
left a comment
There was a problem hiding this comment.
The migration checklist restructuring and single-guide title handling look sound. Two optional documentation improvements inline: document the logging dependency/feature and retain a brief backend-availability reminder.
AI-assisted review.
…rted guide Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…rted guide Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ample Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
PostHog Review · Standard · reviewed 9e8fc3a: 2 Should fix. This pull request is large, so the review ran in 4 parts with less depth than usual.
This is review round 3 on this pull request. When findings keep coming back in the same code, the approach is usually the problem. Before the next fix, check whether a different design would remove the whole class of findings.
…on-guide-structure Stacks the sorted guide on the identify-style person processing default, which also carries the Rust 1.100 Clippy fix. The guide keeps the sorted text. References regenerated. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Proxy pass-through and redirect fixes, flush and shutdown on both lanes, how a null property fills, and a `$set` in the request context. Points the shared capture v1 link at the API reference. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
… ignored The guide said a $process_person_profile property wins over the personless false on any event with a generated distinct ID. It does not when the request context was already applied by hand: RequestContext::event applies it while building the event. The option works there. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Each rustdoc intra-doc link pointed at a slug of its link text, such as `crate::Client::alias` -> #crateclientalias, which no heading on the page has. The generator now labels every heading first and points a link at its target's heading by rustdoc id, or at the type that lists a field or variant. A target with no heading, such as `Client` or `Default`, stays plain code. Links are written inline, since `Self::code` means a different item on each type. All 142 links on the 1.x page now land on a heading, down from 19 dead `#` links and 26 rustdoc paths. docs/capabilities.json still mapped four `Client` flag methods that 1.x removed, so a 1.0.0 run, which checks for stale keys, exited before writing any page. The next-major page no longer gets an " (experimental)" title. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Regenerated from docs/migration-guide-structure (#362) at 1.0.0 after its generator fix. Every intra-doc link now lands on a heading on the page, and links whose target has no heading, such as `Client`, are plain code. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Vincent ruled out self-hosted framing in the guides, and the endpoint and 404 sentences read as self-host framing. The retry tables and the proxy notes stay. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…369) * docs: publish the posthog-rs 1.x reference and migration guide pages Adds references/posthog-rust-1.md and references/posthog-rust-migration.md as the 1.0.0 release will write them, so the Strapi sync puts them on posthog.com before 1.0.0 ships. Both come from running scripts/generate_markdown.py on docs/migration-guide-structure (#362) with the crate at 1.0.0, the version the release sets before it generates. The generator on main writes only the 0.x page and the reference page, and skips the migration page without docs/migration-*.md, so neither file is rewritten before the release. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs: point the Rust 1.x reference's intra-doc links at their headings Regenerated from docs/migration-guide-structure (#362) at 1.0.0 after its generator fix. Every intra-doc link now lands on a heading on the page, and links whose target has no heading, such as `Client`, are plain code. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs: regenerate the migration page without the 404 hint and self-hosted lines Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
66ed402
into
eli/v1-identify-style-person-default
Uh oh!
There was an error while loading. Please reload this page.