Repository navigation
fix: replace personal data and tokens in sample payloads - #83
Merged
Merged
Conversation
Replace values that look like real people's details and tokens in 44 paysafe, pubnub, recruitee, sendbird, signnow, stigg, stream, stuart and workable samples with obvious placeholders. JSON keys, order and formatting are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
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.
Replaces what look like real people's details and tokens in 44 sample payloads published to samples.hookdeck.com. Only the values change: every JSON key and its order is the same, the diff is 132 lines replaced one for one, and the JSON formatting is untouched.
yarn compilesucceeds andyarn testpasses 26 of 26.No real values appear in this PR text or the commit message.
What was replaced
user1@example.comJane Doe,Jane,jane-doe,example_user,Example User,Example Customer,Example Companyhttps://example.com/avatar.png555digits203.0.113.x(RFC 5737)1 Example Street,Suite 100,Example City,Example Region,Example State,Example Country,XXcodes, zeroed postcodes and coordinates1990-01-01, in the sameday/month/yearfieldsexample-tokenand numeric segments zeroedFiles and fields
customerIp,paymentHandleToken,gatewayResponse.sid, and inPAYMENT_HANDLE_EXPIREDprofile.dateOfBirthandbillingDetails. Account and transaction ids are keptdata[0].subKeycandidate.emails[0],candidate.photo_thumb_urlapp_idmeta.callback_url(host and token path). Its query parameter is kept because it repeats the document or group id already in the filecustomer.billingId, andcustomer.nameinentitlements.updatedchannel.created:channel.created_by.id, memberid,user_id,name,first_name,last_name,image, and the same id atuser.id.user.idinchannel.muted,user.banned,user.deactivated,user.reactivated,user.unread_message_reminder,user.updated, and wherever else that id repeatsdetails.package.client_tracking_url,end_customer_tracking_url, anddetails.courier.nameincourier_assignedupdated_by,personal_email[0].value,address,employeeFormStep.address,phone,phone_group[0].value.phone,preferred_name,social_profiles[0].urland.username,social_profiles[2].url,profile_url,accountWorth a look
customer.updated'schanges.emailwas alreadyuser1@example.com.channel.mutednames: the id repeats insidenameatuser,mute.userandmute.channel.created_by, so those whole names becameExample User.statuslooks like a geocoder status rather than a location, andstreet_nameandstreet_numberare empty.phone_group'srow_idandphone_typeare also kept.Checks
mainshows only the intended values differ.Git history: not rewritten
The old values stay in public git history, as with #82. This PR doesn't change that.
🤖 Generated with Claude Code