Skip to content

Comments

Updated Inspecotor debugger to support session filtering and more acc…#1630

Merged
thoragudf merged 10 commits intomainfrom
inspector-debugger-get-started
Feb 19, 2026
Merged

Updated Inspecotor debugger to support session filtering and more acc…#1630
thoragudf merged 10 commits intomainfrom
inspector-debugger-get-started

Conversation

@thoragudf
Copy link
Contributor

@thoragudf thoragudf commented Feb 9, 2026

…essible setup docs.


Note

Low Risk
Documentation-only changes; primary risk is user confusion from updated anchors/min-version guidance if any links or version requirements are incorrect.

Overview
Adds and documents session filtering in the Inspector Debugger, replacing the prior “coming soon” notes with concrete instructions for identifying a Stream ID and filtering the live event stream by session.

Reorganizes “advanced debugger features” docs by introducing a dedicated Enabling advanced debugger features section (including key generation guidance) and updating cross-links across Segment/web/iOS/Android setup pages; also updates the stated minimum Web SDK version for these advanced features to 3.0.0+.

Written by Cursor Bugbot for commit 14c4829. This will update automatically on new commits. Configure here.

Summary by CodeRabbit

  • Documentation
    • Updated Inspector Debugger docs: added installation notice, marked debugger for development/staging, and replaced "coming soon" with Stream session filter details.
    • Reorganized "Enabling advanced debugger features" to unify Property value validation and Session filtering, with concise setup guidance and encryption-key notes.
    • Added Property value validation sections to Android, iOS, and web SDK references and updated cross-links and event-finding guidance to include session-based filtering.

@vercel
Copy link

vercel bot commented Feb 9, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Feb 19, 2026 1:36pm

Request Review

@coderabbitai
Copy link

coderabbitai bot commented Feb 9, 2026

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
📝 Walkthrough

Walkthrough

Consolidates and reorganizes Inspector Debugger docs: merges Property value validation and Session filtering under a new "Enabling advanced debugger features" section, replaces placeholder text, clarifies session filtering and event-finding guidance, and adds platform-specific Property value validation docs for Android and iOS; minor link update for web and connection docs.

Changes

Cohort / File(s) Summary
Inspector Debugger docs
pages/inspector/inspector-debugger.mdx
Reorganized content: added "Enabling advanced debugger features" (covers Property value validation and Session filtering), added usage callout, replaced "coming soon" stream session text, expanded session-filtering instructions, and updated supported SDKs table and links.
Inspector connection note
pages/inspector/connect-inspector-to-segment.mdx
Updated hyperlink target to point to the new "Enabling advanced debugger features" anchor.
Android SDK docs
pages/reference/avo-inspector-sdks/android.mdx
Added "Property value validation" section with availability, enablement steps, key generation/workflow guidance, and initialization notes (documentation only).
iOS SDK docs
pages/reference/avo-inspector-sdks/ios.mdx
Added "Property value validation" section with feature description, requirements, enablement steps, key handling guidance, and security callouts (documentation only).
Web SDK docs
pages/reference/avo-inspector-sdks/web.mdx
Updated hyperlink to the new "Enabling advanced debugger features" anchor (no logic changes).

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

Suggested reviewers

  • logason
  • aleks-tpom6oh
  • bjornj12

Poem

🐰 Hopping through new docs, I cheer,
Features gathered, tidy and near.
Sessions found and values shown,
Advanced flags now brightly known.
A tiny hop — the debugger’s clear!

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title references session filtering and advanced features, which are the main changes documented across the pull request.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch inspector-debugger-get-started

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@logason
Copy link
Member

logason commented Feb 9, 2026

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

This is the final PR Bugbot will review for you during this billing cycle

Your free Bugbot reviews will reset on March 4

Details

Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
pages/inspector/inspector-debugger.mdx (1)

13-13: ⚠️ Potential issue | 🟡 Minor

Fix duplicate word in sentence.

“the the” → “the”.

🤖 Fix all issues with AI agents
In `@pages/inspector/inspector-debugger.mdx`:
- Around line 165-201: Update the section to correct inaccuracies: change the
Inspector Web SDK version mention from v1.5.0+ to v2.1.0, remove any wording
that presents "Session filtering" as a client-side SDK feature and instead
describe it as Inspector UI filtering (URL-based filters and Saved Views), and
clarify that Property value validation only works in Dev/Staging environments,
requires configuring publicEncryptionKey, and only operates when using
trackSchemaFromEvent() (not trackSchema()). Replace the supported SDKs list with
the complete, current list (Web v2.1.0, Android v2.3.0, iOS v2.0.1, React Native
v1.3.1, Node.js v1.1.1, Java v1.1.1, Go v0.9.0, Dart v1.0.0) and add
integrations (Segment, RudderStack, PostHog, GTM, Snowplow, Adobe); keep UI
instructions about enabling the setting and generating keys unchanged.

@thoragudf thoragudf marked this pull request as ready for review February 18, 2026 11:35
@thoragudf
Copy link
Contributor Author

@coderabbitai please re-review

@coderabbitai
Copy link

coderabbitai bot commented Feb 19, 2026

@thoragudf: I'll re-review the PR changes for you.

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

coderabbitai[bot]
coderabbitai bot previously requested changes Feb 19, 2026
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 7

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@pages/inspector/inspector-debugger.mdx`:
- Around line 199-207: Update the platform/versions table so it only lists
released SDK versions or clearly marks unreleased ones: replace the iOS
CocoaPods "2.2.1+" entry with the actual released version "1.2.5+" (or remove
it) and replace the iOS SPM "1.5.0+" entry with the released "1.3.3+" (or mark
both iOS CocoaPods and iOS SPM rows as "coming soon / unreleased" if those newer
versions are intended but not yet published); keep Android "2.4.0+" as-is and
ensure the table cell text for the iOS CocoaPods and iOS SPM rows is updated to
match this change in the inspector-debugger.mdx content.

In `@pages/reference/avo-inspector-sdks/android.mdx`:
- Around line 106-108: The documentation references passing a publicKey to
AvoInspector but the Initialization section's constructor signatures (public
AvoInspector(String apiKey, Application application, AvoInspectorEnv env,
`@Nullable` Activity rootActivityForVisualInspector) and Kotlin class
AvoInspector(...)) do not include a publicKey parameter; update the
Initialization section to include the new constructor overload that accepts a
publicKey (e.g., add the Java signature including a publicKey String parameter
and the corresponding Kotlin constructor parameter) or add an explicit example
showing how to pass publicKey when constructing AvoInspector so readers can see
the exact call site.
- Line 76: The file is missing the Callout component import which causes the
<Callout> blocks to not render; add the same import used in ios.mdx (the Callout
component) at the top of android.mdx so the <Callout> usages (around the blocks
currently at ~80–82 and ~110–112) resolve correctly and render; ensure the
import name matches the <Callout> tag exactly and follows the pattern used for
other shared components in the document.
- Around line 80-82: The Callout about property value validation currently
claims "version 2.4.0+" which is unreleased; update the Callout (the <Callout
type="info" emoji="💡"> block referencing property value validation) to either
defer the section until 2.4.0 is released or change the text to correctly
reflect the current SDK (e.g., say the feature is available in 2.1.0 or mark it
as "coming in 2.4.0" / gated) so users aren’t misled; modify the callout content
to accurately state availability and, if gating, add a short note indicating the
feature will be enabled when Android Inspector SDK 2.4.0 is released.

In `@pages/reference/avo-inspector-sdks/ios.mdx`:
- Around line 84-86: The documentation shows an outdated AvoInspector
initializer (init(apiKey: String?, env: AvoInspectorEnv)) but the guide refers
to passing a public key; update the Initialization section to include the new
public key parameter or add a clear example showing how to pass it to
AvoInspector (e.g., reference the AvoInspector initializer signature to include
publicKey or publicEncryptionKey) so readers can instantiate AvoInspector with
the public key when following Step 3.
- Line 54: The file is missing an import for Callout and has a
constructor/signature mismatch for AvoInspector; add an import for Callout from
'nextra/components' at the top of pages/reference/avo-inspector-sdks/ios.mdx so
the two <Callout> blocks render correctly, and update the Initialization
documentation to match the actual initializer that accepts the public key (or
clarify the correct usage) — adjust the documented signature shown under
Initialization (currently init(apiKey: String?, env: AvoInspectorEnv)) to
include the public key parameter used in Step 3 or change Step 3 to the true
constructor call for AvoInspector so the code examples and text are consistent.
- Around line 58-60: Update the Callout in ios.mdx that currently claims
"Property value validation is available for version 5.2.6+" to the verified
minimums from inspector-debugger.mdx: specify iOS CocoaPods: 2.2.1+ and iOS SPM:
1.5.0+ (modify the <Callout ...> text so it lists those two channel-specific
minimum versions instead of the non-existent 5.2.6+).

Co-authored-by: Aleks Verein <aleks-tpom6oh@users.noreply.github.com>
Co-authored-by: Aleks Verein <aleks-tpom6oh@users.noreply.github.com>
cursoragent and others added 3 commits February 19, 2026 13:34
Co-authored-by: Aleks Verein <aleks-tpom6oh@users.noreply.github.com>
Co-authored-by: Aleks Verein <aleks-tpom6oh@users.noreply.github.com>
Co-authored-by: Aleks Verein <aleks-tpom6oh@users.noreply.github.com>
@logason logason dismissed coderabbitai[bot]’s stale review February 19, 2026 14:04

We resolved the issue they requested changes for


```swift
init(apiKey: String?, env: AvoInspectorEnv)
init(apiKey: String, env: AvoInspectorEnv, proxyEndpoint: String, publicEncryptionKey: String?)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
init(apiKey: String, env: AvoInspectorEnv, proxyEndpoint: String, publicEncryptionKey: String?)
init(apiKey: String, env: AvoInspectorEnv, proxyEndpoint: String?, publicEncryptionKey: String?)

@thoragudf thoragudf merged commit 6ee89ba into main Feb 19, 2026
4 checks passed
@thoragudf thoragudf deleted the inspector-debugger-get-started branch February 19, 2026 15:03
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.

4 participants