Closed
Conversation
Member
Author
PR Evaluation ReportSummaryAdds comprehensive PostHog analytics integration to a Next.js 15 todo app with event tracking for user actions, page views, and error handling
PostHog Integration: 9/10Events Tracked: todo_created, todo_completed, todo_uncompleted, todo_deleted, todo_create_failed, todo_update_failed, todo_delete_failed, todo_fetch_failed, todo_form_submitted, about_page_viewed Issues⚪ LOW: Missing user identification setup - no posthog.identify() calls found (in
Strengths
Runnability: 8/10
Issues
Code Quality: 9/10
Overall Score: 9/10Recommendation: ✅ APPROVE Generated by PR Evaluation Agent |
Member
Author
PR Evaluation ReportSummaryThis PR adds comprehensive PostHog analytics integration to a Next.js 15 App Router todo application. It includes client-side initialization via instrumentation-client.ts, server-side PostHog client setup, reverse proxy configuration to avoid ad-blockers, and event tracking for all core todo CRUD operations plus page views. The implementation also includes a .posthog-events.json manifest documenting all tracked events.
PostHog Integration: 4/5Events Tracked: todo_created, todo_completed, todo_uncompleted, todo_deleted, todo_create_failed, todo_update_failed, todo_delete_failed, todo_fetch_failed, todo_form_submitted, about_page_viewed Issues🟡 MEDIUM: Missing user identification - no posthog.identify() call to link events to users (in
⚪ LOW: No automatic pageview tracking configured - only manual about_page_viewed event (in
⚪ LOW: Server-side PostHog client is created but never used in the PR (in
Strengths
Code Quality: 5/5
Quality of Insights: 5/5
Strengths
Overall Score: 4/5Recommendation: ✅ APPROVE Generated by PR Evaluation Agent |
Member
Author
PR Evaluation ReportSummaryThis PR implements a comprehensive PostHog analytics integration for a Next.js 15 App Router todo application. It includes client-side initialization using the modern instrumentation-client.ts pattern, reverse proxy setup to circumvent ad-blockers, server-side PostHog client setup, and extensive event tracking across core todo CRUD operations (create, complete, delete) with error tracking. The implementation also includes a page view tracker component and documents all events in a .posthog-events.json manifest file.
Important Files Changed
PostHog Integration: 4/5Events Tracked: todo_created, todo_completed, todo_uncompleted, todo_deleted, todo_create_failed, todo_update_failed, todo_delete_failed, todo_fetch_failed, todo_form_submitted, about_page_viewed Issues
Criteria met
Code Quality: 5/5
Quality of Insights: 5/5
Strengths
Overall Score: 5/5Recommendation: ✅ APPROVE Generated by PR Evaluation Agent |
Member
Author
|
Now I have all the information I need to provide a thorough evaluation. Here's my review: PR Evaluation ReportSummaryThis PR adds PostHog analytics integration to a Next.js 15 App Router todo application. It implements client-side tracking via
Important Files Changed
PostHog Integration: 2/5Events Tracked: todo_created, todo_completed, todo_uncompleted, todo_deleted, todo_create_failed, todo_update_failed, todo_delete_failed, todo_fetch_failed, todo_form_submitted, about_page_viewed Error Tracking: ✅ Configured via Issues
Criteria Met
Code Quality: 3/5
Issues
Quality of Insights: 4/5
Strengths
Issues
Overall Score: 3/5Recommendation: ❌ REQUEST CHANGES Required Changes Before Merge:
Recommended Improvements:
Generated by PR Evaluation Agent |
Member
Author
|
Now I have all the information needed to provide a comprehensive evaluation. Let me create the PR review: PR Evaluation ReportSummaryThis PR adds PostHog analytics integration to a Next.js 15 App Router todo application. It implements client-side event tracking for todo CRUD operations, page views, and error capture, along with a reverse proxy configuration to bypass ad blockers. However, the PostHog SDK dependencies are missing from
Important Files Changed
PostHog Integration: 3/5
Issues
Other completed criteria
Code quality: 3/5
Issues
Quality of insights: 4/5PostHog insights enabled
Issues
Overall score: 3/5Recommendation: ❌ REQUEST CHANGES Required changes:
Recommended improvements:
|
|
This issue has 3216 words at 5 comments. Issues this long are hard to read or contribute to, and tend to take very long to reach a conclusion. Instead, why not:
Is this issue intended to be sprawling? Consider adding label |
Member
Author
|
Now I have a complete picture. Let me provide the evaluation: PR Evaluation ReportSummaryThis PR adds PostHog analytics integration to a Next.js 15 App Router todo application. It implements client-side tracking via
Overall confidence score: 2/5 ❌Required changes:
Recommended improvements:
Important Files Changed
PostHog Integration: 2/5
Issues
Other completed criteria#### Other completed criteria
Code quality: 3/5
Issues
Quality of PostHog insights: 4/5
Issues
Sequence diagramsequenceDiagram
participant User
participant Browser
participant NextJS as Next.js App
participant Proxy as /ingest (Reverse Proxy)
participant PostHog as PostHog Cloud
Note over Browser: App loads instrumentation-client.ts
Browser->>Browser: posthog.init() with capture_exceptions: true
User->>Browser: Visit About Page
Browser->>Browser: AboutPageTracker mounts
Browser->>Proxy: capture('about_page_viewed')
Proxy->>PostHog: Forward to us.i.posthog.com
User->>Browser: Submit Todo Form
Browser->>Browser: capture('todo_form_submitted', {has_description, title_length})
Browser->>NextJS: POST /api/todos
NextJS-->>Browser: 200 OK (newTodo)
Browser->>Proxy: capture('todo_created', {todo_id, has_description})
Proxy->>PostHog: Forward event
User->>Browser: Toggle Todo Complete
Browser->>NextJS: PATCH /api/todos/:id
NextJS-->>Browser: 200 OK
Browser->>Proxy: capture('todo_completed', {todo_id})
Proxy->>PostHog: Forward event
User->>Browser: Delete Todo
Browser->>NextJS: DELETE /api/todos/:id
NextJS-->>Browser: 200 OK
Browser->>Proxy: capture('todo_deleted', {todo_id})
Proxy->>PostHog: Forward event
Note over Browser,PostHog: Error Flow
Browser->>NextJS: API Request
NextJS-->>Browser: Error/Exception
Browser->>Proxy: capture('todo_*_failed', {error_message})
Browser->>Proxy: captureException(error)
Proxy->>PostHog: Forward error events
|
Member
Author
|
Now I have all the information needed to provide a comprehensive PR evaluation. Here's the report: PR Evaluation ReportSummaryThis PR adds PostHog analytics integration to a Next.js 15 App Router todo application. It includes client-side tracking via
Confidence score: 2/5 ❌Recommended changes and improvements (in order of most urgent):
Important files changed
App sanity check
Issues
|
| Criteria | Result |
|---|---|
| PostHog SDKs installed | ❌ Not installed - missing from package.json |
| PostHog client initialized | instrumentation-client.ts (Next.js 15 pattern) but has invalid config option |
| capture(): | ✅ Configured - 10 events tracked across components |
| identify(): | ❌ Not configured - No user identification implemented |
| Error tracking: | ✅ Configured - capture_exceptions: true and posthog.captureException() calls |
| Reverse proxy: | ✅ Configured - Correct rewrites in next.config.ts for /ingest/* |
Issues
- [CRITICAL] Missing dependencies: The integration imports
posthog-jsandposthog-nodebut neither is added topackage.json. The app cannot build. - [CRITICAL] Invalid init config: The
defaults: '2025-05-24'option is not a valid PostHog configuration parameter. - [MEDIUM] No user identification: Without
posthog.identify(), all events are attributed to anonymous users, limiting cohort analysis and user journey tracking. - [MEDIUM] Dead server code:
lib/posthog-server.tsexportsgetPostHogClient()andshutdownPostHog()but they're never called.
Other completed criteria
- Reverse proxy correctly routes
/ingest/*tous.i.posthog.com - Static assets proxy configured for
/ingest/static/* skipTrailingSlashRedirect: trueadded for PostHog compatibilityui_hostcorrectly set tohttps://us.posthog.com- Debug mode enabled for development environment
- Exception capture enabled globally
Quality of PostHog insights: 4/5
| Filename | Captured events | Description |
|---|---|---|
todo-list.tsx |
todo_created, todo_completed, todo_uncompleted, todo_deleted, todo_fetch_failed, todo_create_failed, todo_update_failed, todo_delete_failed + captureException |
Comprehensive CRUD tracking with success/failure states; enables funnel analysis for todo completion rates |
todo-form.tsx |
todo_form_submitted |
Form submission with has_description, title_length, description_length properties for input analysis |
about-page-tracker.tsx |
about_page_viewed |
Page view tracking with deduplication; useful for awareness funnel |
Issues
- [LOW] Redundant event tracking:
todo_form_submittedandtodo_createdboth fire on successful todo creation. Consider tracking only one or differentiating their purposes (intent vs. success). - [LOW] Missing page view for main page: Only the About page has explicit tracking. The main todo list page has no
$pageviewequivalent.
Other completed criteria
- Events capture meaningful user actions (create, complete, delete todos)
- Error events include
error_messageproperty for debugging todo_idincluded for correlation across events- Boolean properties (
has_description) enable segmentation - Numeric properties (
title_length) enable distribution analysis - Separate events for
todo_completedvstodo_uncompletedenable completion rate analysis .posthog-events.jsondocuments all events with descriptions for team reference
Reviewed by wizard workbench PR evaluator
Member
Author
|
Now I have all the information needed to provide a comprehensive evaluation. Here is my PR review: PR Evaluation ReportSummaryThis PR adds PostHog analytics integration to a Next.js 15 App Router todo application. It implements client-side tracking via
Confidence score: 2/5 ❌Top recommended changes:
Important files changed
App sanity check
Issues
|
| Criteria | Result |
|---|---|
| PostHog SDKs installed | No - posthog-js and posthog-node not in package.json |
| PostHog client initialized | Partial - instrumentation-client.ts has init code but uses invalid defaults option |
| capture() | Yes - Multiple capture calls for todo CRUD and page views |
| identify() | No - No user identification implemented |
| Error tracking | Yes - capture_exceptions: true and posthog.captureException() calls |
| Reverse proxy | Yes - Correctly configured in next.config.ts with /ingest rewrites |
Issues
- Missing SDK installation: Add to package.json:
"posthog-js": "^1.x.x"and"posthog-node": "^4.x.x". [CRITICAL] - No user identification: Add
posthog.identify(userId)when user context is available to link events to users. [MEDIUM] - Invalid defaults option: Remove
defaults: '2025-05-24'from init config or replace with valid options likepersistence: 'localStorage'. [MEDIUM] - Server client unused: Either implement server-side tracking or remove
lib/posthog-server.tsto avoid dead code. [LOW]
Other completed criteria
- API host points to reverse proxy (
/ingest) - UI host correctly set to
https://us.posthog.com - Debug mode enabled in development
- Exception capture enabled
- Environment variables documented in
.env - Proper error message extraction in catch blocks
Quality of PostHog insights: 4/5
| Filename | Captured events | Description |
|---|---|---|
todo-list.tsx |
todo_created, todo_completed, todo_uncompleted, todo_deleted, todo_fetch_failed, todo_create_failed, todo_update_failed, todo_delete_failed + captureException |
Comprehensive CRUD tracking with success/failure states, enables funnel analysis and error monitoring |
todo-form.tsx |
todo_form_submitted |
Tracks form submissions with useful properties (has_description, title_length) |
about-page-tracker.tsx |
about_page_viewed |
Page view tracking with deduplication via ref |
Issues
- Missing automatic pageview tracking: Consider enabling
capture_pageview: trueor implementing pageviews for all routes, not just the about page. [MEDIUM] - No session recording setup: Consider adding
enable_recording_console_logor session replay for debugging. [LOW]
Other completed criteria
- Events follow consistent snake_case naming convention
- Events are enriched with contextual properties (todo_id, error_message, has_description, title_length)
- Error events paired with
captureExceptionfor full error context - Events map to real user actions (create, complete, delete)
- Events enable funnel analysis (form_submitted → created vs created_failed)
- Event documentation in
.posthog-events.jsonprovides good discoverability
Reviewed by wizard workbench PR evaluator
Member
Author
|
Now I have all the information needed to evaluate this PR. Let me compile the review: PR Evaluation ReportSummaryThis PR adds PostHog analytics integration to a Next.js 15 App Router todo application. It includes client-side initialization via
Confidence score: 2/5 ❌Top recommended changes:
Important files changed
App sanity check score: 2/5
Issues
|
| Criteria | Result | Description |
|---|---|---|
| PostHog SDKs installed | No | Neither posthog-js nor posthog-node are in package.json |
| PostHog client initialized | Partial | instrumentation-client.ts initializes client correctly but uses undocumented defaults: '2025-05-24' option |
| capture() | Yes | Multiple events captured: todo_created, todo_completed, todo_deleted, etc. |
| identify() | No | No posthog.identify() calls for user identification |
| Error tracking | Yes | captureException() used in all error handlers with capture_exceptions: true in init |
| Reverse proxy | Yes | Proper /ingest rewrites in next.config.ts with skipTrailingSlashRedirect |
Issues
- Missing
posthog-jsdependency: The package is not installed. Runnpm install posthog-js. [CRITICAL] - Missing
posthog-nodedependency: The package is not installed. Runnpm install posthog-node. [CRITICAL] - No
posthog.identify()implementation: User identification is missing, which limits the ability to track user journeys and build cohorts. Addposthog.identify(userId)when users are authenticated. [MEDIUM] - Undocumented
defaultsoption:instrumentation-client.tsusesdefaults: '2025-05-24'which is not a documented PostHog option. This may cause unexpected behavior or be ignored. [MEDIUM] - Server client inconsistent host config:
lib/posthog-server.tsusesprocess.env.NEXT_PUBLIC_POSTHOG_HOSTdirectly while client uses/ingestproxy. Server should use the direct PostHog host. [LOW]
Other completed criteria
- Correct API host configuration via reverse proxy
capture_exceptions: trueenabled for automatic error tracking- Debug mode enabled in development
ui_hostcorrectly set for US region- Proper deduplication in
AboutPageTrackerusinguseRef - No PII in event properties
PostHog insights score: 4/5
| Filename | PostHog events | Description |
|---|---|---|
todo-list.tsx |
todo_created, todo_completed, todo_uncompleted, todo_deleted, todo_fetch_failed, todo_create_failed, todo_update_failed, todo_delete_failed |
Comprehensive CRUD tracking with error states. Enables funnel analysis for todo lifecycle and error rate monitoring. |
todo-form.tsx |
todo_form_submitted |
Form submission with has_description, title_length, description_length properties. Enables analysis of user input patterns. |
about-page-tracker.tsx |
about_page_viewed |
Page view tracking for awareness funnel analysis. |
Issues
- Duplicate form submission tracking: Both
todo_form_submittedandtodo_createdfire on successful todo creation. Consider removingtodo_form_submittedor making it capture intent regardless of success. [LOW] - Missing automatic pageview tracking: No
capture_pageviewoption set in init. Relies on customabout_page_viewedevent only. Consider enabling automatic pageviews or adding manual tracking to all pages. [MEDIUM] - No session replay or feature flag setup: Could enhance analytics with session replay for debugging user flows. [LOW]
Other completed criteria
- Events enriched with relevant properties (
todo_id,has_description,title_length, etc.) - Error events include
error_messagefor debugging - Events represent real user actions (create, complete, delete)
- Success/failure states tracked separately
.posthog-events.jsonprovides good documentation for all events
Reviewed by wizard workbench PR evaluator
Member
Author
|
Now I have all the information needed to evaluate this PR. Let me compile my review: PR Evaluation ReportSummaryThis PR adds PostHog analytics integration to a Next.js 15 App Router todo application. It implements client-side tracking via
Confidence score: 2/5 ❌
Files changed
App sanity check score: 2/5 ❌
Issues
|
| Criteria | Result | Description |
|---|---|---|
| PostHog SDKs installed | No | Neither posthog-js nor posthog-node appear in package.json dependencies |
| PostHog client initialized | Yes | Client initialized in instrumentation-client.ts using Next.js 15 instrumentation pattern with api_host pointing to reverse proxy |
| capture() | Yes | Events captured for all CRUD operations, form submission, page view, and errors |
| Identify() | No | No user identification implemented anywhere |
| Error tracking | Yes | Uses posthog.captureException(error) in all catch blocks plus capture_exceptions: true in init |
| Reverse proxy | Yes | Properly configured via Next.js rewrites to /ingest/* → us.i.posthog.com with static asset handling |
Issues
- Missing NPM dependencies:
posthog-jsandposthog-nodemust be added to package.json for the integration to work. [CRITICAL] - No user identification:
posthog.identify()is not called anywhere. User sessions won't be linked across devices or to user accounts. Add identification after authentication. [MEDIUM] - Suspicious
defaultsconfig option:defaults: '2025-05-24'in init is not a standard PostHog config option. May be ignored or cause issues. [LOW] - Server client configured but unused:
lib/posthog-server.tscreates a PostHog Node client but it's never used for server-side tracking. [LOW]
Other completed criteria
- Uses correct US region endpoints (us.i.posthog.com, us-assets.i.posthog.com)
- Debug mode enabled only in development
- Proper
skipTrailingSlashRedirectfor PostHog API compatibility - Uses environment variables for API key configuration
- No PII in event properties (only has todo_id, lengths, error messages)
PostHog insights score: 4/5 ✅
| Filename | PostHog events | Description |
|---|---|---|
todo-list.tsx |
todo_created, todo_completed, todo_uncompleted, todo_deleted |
Core product engagement metrics for todo lifecycle - enables funnel analysis and completion rates |
todo-list.tsx |
todo_fetch_failed, todo_create_failed, todo_update_failed, todo_delete_failed |
Error tracking events with error messages - enables reliability monitoring and debugging |
todo-list.tsx |
captureException |
Exception capture for all CRUD failures - provides stack traces for debugging |
todo-form.tsx |
todo_form_submitted |
Form submission with has_description, title_length, description_length - enables analysis of user input patterns |
about-page-tracker.tsx |
about_page_viewed |
Page view tracking - enables awareness funnel analysis |
Issues
- No automatic pageview tracking: Only
about_page_viewedis manually tracked. Consider enablingcapture_pageview: trueor implementing a pageview capture in the layout for comprehensive navigation analytics. [MEDIUM] - Limited property enrichment on success events:
todo_completedandtodo_deletedonly capturetodo_id. Could include more context like time_since_creation for completion analysis. [LOW]
Other completed criteria
- Events capture real user actions (create, complete, delete todos)
- Error events include error messages for debugging
- Success events include relevant properties (todo_id, has_description, title_length)
- Events documented in
.posthog-events.jsonfor reference - Events enable key product questions: "What % of todos get completed?", "How often do users add descriptions?", "What errors are users encountering?"
Reviewed by wizard workbench PR evaluator
Member
Author
|
Now I have all the information needed to write the PR evaluation. Let me produce the comprehensive review: PR Evaluation ReportSummaryThis PR adds PostHog analytics integration to a Next.js 15 App Router todo application. It implements client-side initialization via
Confidence score: 3/5 🤔
File changes
App sanity check: 2/5 ❌
Issues
|
| Criteria | Result | Description |
|---|---|---|
| PostHog SDKs installed | No | Packages imported but not in package.json dependencies |
| PostHog client initialized | Yes | Uses instrumentation-client.ts with posthog.init(), api_host pointing to reverse proxy |
| capture() | Yes | 10 events tracked across todo CRUD and page views |
| identify() | No | No user identification implemented |
| Error tracking | Yes | Uses posthog.captureException() for caught errors plus capture_exceptions: true in config |
| Reverse proxy | Yes | Properly configured in next.config.ts with /ingest route to us.i.posthog.com |
Issues
- Missing SDK packages in dependencies: Without adding
posthog-jsandposthog-nodetopackage.json, the app will fail to build. [CRITICAL] - No posthog.identify() calls: User sessions are anonymous. Add identification when user context is available (e.g., after authentication or using distinct_id). [MEDIUM]
- Nonstandard
defaultsoption:defaults: '2025-05-24'is not a valid PostHog init option. This may be ignored or cause unexpected behavior. Consider removing or using valid options likepersistence. [MEDIUM] - No automatic pageview capture: Missing
capture_pageview: truein init options. Currently only the About page tracks views explicitly. [LOW]
Other completed criteria
- Correct API host configuration using reverse proxy (
/ingest) - UI host configured separately (
ui_host: 'https://us.posthog.com') - Debug mode enabled in development
- Exception auto-capture enabled
skipTrailingSlashRedirect: trueset for PostHog API compatibility- Proper cleanup pattern using
useRefto prevent duplicate event firing
PostHog insights and events: 4/5 ✅
| Filename | PostHog events | Description |
|---|---|---|
todo-list.tsx |
todo_created, todo_completed, todo_uncompleted, todo_deleted, todo_fetch_failed, todo_create_failed, todo_update_failed, todo_delete_failed |
Full CRUD lifecycle with success/failure tracking. Includes todo_id, error_message, and contextual properties. Enables funnel analysis (create → complete → delete) and error rate monitoring. |
todo-form.tsx |
todo_form_submitted |
Captures form submission intent with has_description, title_length, description_length. Useful for understanding user input patterns. |
about-page-tracker.tsx |
about_page_viewed |
Tracks About page engagement. Useful for awareness funnel. |
Issues
- Duplicate event for todo creation: Both
todo_form_submitted(in form) andtodo_created(in list) fire when creating a todo. This is intentional (form submission vs. API success) but may cause confusion in analysis. [LOW] - No session/user context: Events lack user identifiers, making cohort analysis and user journey tracking impossible. [MEDIUM]
Other completed criteria
- Events represent real user actions (create, complete, delete todos)
- Error events capture actionable context (error_message, todo_id)
- Properties are non-PII safe (lengths, booleans, IDs)
- Event naming follows snake_case convention consistently
- Success and failure states tracked separately for operational insights
- Events enable building insights: completion rate, error rate, user engagement
Reviewed by wizard workbench PR evaluator
Member
Author
|
Now I have all the information needed to evaluate this PR. Let me compile the evaluation report. PR Evaluation ReportSummaryThis PR adds PostHog analytics integration to a Next.js 15 todo application. It implements client-side initialization via
Confidence score: 2/5 ❌
File changes
App sanity check: 2/5 ❌
Issues
|
| Criteria | Result | Description |
|---|---|---|
| PostHog SDKs installed | No | posthog-js and posthog-node are imported but not in package.json dependencies |
| PostHog client initialized | Yes | Client initialized in instrumentation-client.ts using Next.js 15 instrumentation pattern with /ingest proxy host |
| capture() | Yes | Multiple posthog.capture() calls for user actions (form submit, CRUD operations) |
| identify() | No | No user identification implemented |
| Error tracking | Yes | posthog.captureException(error) called on all catch blocks, capture_exceptions: true in init config |
| Reverse proxy | Yes | Correct rewrites in next.config.ts for /ingest to us.i.posthog.com and static assets |
Issues
- PostHog packages not installed: Dependencies are imported but not added to package.json. App will crash on import. [CRITICAL]
- No user identification:
posthog.identify()is never called. User analytics will be anonymous only. [MEDIUM] - Server-side client unused:
posthog-nodeclient configured but never utilized for server-side event tracking. [MEDIUM]
Other completed criteria
- Uses
instrumentation-client.tswhich is the correct Next.js 15 pattern ui_hostcorrectly set tohttps://us.posthog.com- Debug mode enabled in development
- Reverse proxy includes both API and static asset paths
skipTrailingSlashRedirect: truecorrectly set for PostHog compatibility- Exception capture enabled via
capture_exceptions: true - Uses
useRefguard in AboutPageTracker to prevent React Strict Mode double-fire
PostHog insights and events: 4/5 ✅
| Filename | PostHog events | Description |
|---|---|---|
todo-form.tsx |
todo_form_submitted |
Captures form submission with properties: has_description, title_length, description_length. Useful for understanding input behavior |
todo-list.tsx |
todo_created, todo_completed, todo_uncompleted, todo_deleted |
Full CRUD lifecycle tracking with todo_id property. Enables funnel analysis |
todo-list.tsx |
todo_fetch_failed, todo_create_failed, todo_update_failed, todo_delete_failed |
Error events with error_message property plus captureException for stack traces. Good error monitoring |
about-page-tracker.tsx |
about_page_viewed |
Page view tracking for navigation analytics |
Issues
- No page view on main page: The home/todo list page doesn't track page views, only the About page does. [LOW]
- Missing funnel completion context: Events like
todo_completeddon't include time-based properties (e.g., time since creation) that would enable richer funnel analysis. [LOW]
Other completed criteria
- Events represent real user actions (create, complete, delete todos)
- Error events capture failure context with error messages
- Event properties are relevant and non-PII (lengths, booleans, IDs)
- Events documented in
.posthog-events.jsonfor team reference - Both success and failure paths are tracked
captureExceptionused for full error stack traces
Reviewed by wizard workbench PR evaluator
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.