analytics domain override#1209
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Greptile SummaryImplemented analytics domain override functionality to route analytics and session replay requests to a separate domain ( Key changes:
The implementation correctly handles both production (uses separate analytics domain) and development (uses same domain) environments. Confidence Score: 5/5
Important Files Changed
Flowchartflowchart TD
A[Client Request] --> B{Request Type?}
B -->|Analytics/Replays| C[getAnalyticsApiUrl]
B -->|Regular API| D[getApiUrl]
C --> E{Environment?}
E -->|Production| F[r.stack-auth.com/api/v1]
E -->|Development| G[Regular Base URL/api/v1]
D --> H[Regular Base URL/api/v1]
F --> I[sendClientRequest with apiUrlOverride]
G --> I
H --> J[sendClientRequest without override]
I --> K[Execute Request]
J --> K
Last reviewed commit: fb49d11 |
No description provided.