testapp: honor eventCaptureBaseUrl from e2e configure payload#131
Merged
Conversation
schematic-bot
approved these changes
Jun 3, 2026
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
2 participants
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.
The sdk-e2e harness passes
eventCaptureBaseUrlin the/configurepayload, but the testapp never mapped it into SDK options, so the SDK fell back to its default capture endpoint (productionc.schematichq.com). All events from e2e runs against dev silently vanished into prod, which made every event-dependent test (TestIdentify,TestTrackEvent, and the new metric-propagation case in SchematicHQ/actions#472) fail or time out.Verified locally: with this fix, the full sdk-e2e suite passes in datastream mode against
api.schematichq.dev.