Disable Reo copy tracking - #940
Draft
zahlekhan wants to merge 1 commit into
Draft
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
What changed
dnt: ["copy"]when initializing the Reo docs beaconWhy
Reo copy tracking can transmit copied command contents, including API keys embedded in commands. The SDK's copy-specific do-not-track option prevents those copy events from being collected while preserving other analytics.
Validation
pnpm exec prettier --check docs/app/providers.tsxpnpm --filter @openuidev/docs exec eslint app/providers.tsxgit diff --checkThe repository-wide docs format check still reports 54 pre-existing formatting failures. The docs type check reaches TypeScript but cannot resolve unbuilt internal workspace packages in a fresh checkout.