-
Notifications
You must be signed in to change notification settings - Fork 721
Adh user apis #530
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
phoenixy1
wants to merge
10
commits into
master
Choose a base branch
from
adh-user-apis
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Adh user apis #530
Conversation
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
Updates the Node.js quickstart to support the new user creation flow: - Default to sending identity object with proper schema (name, emails, phone_numbers, addresses) - Auto-retry with consumer_report_user_identity on INVALID_FIELD error - Track both user_id and user_token from responses - Use user_token when available (from consumer_report_user_identity), otherwise user_id - Remove user.client_user_id when passing user_id/user_token to link token creation - Update CRA endpoints to use correct identifier (user_token or user_id) - Income endpoints always use user_token as required - Upgrade plaid library to v40.0.0 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Updated all backend implementations (Python, Node.js, Go, Java, Ruby) to support both old-style (user_token) and new-style (user_id) CRA user integrations. Each backend now tries the Identity field first, then falls back to ConsumerReportUserIdentity if that fails. All CRA endpoints (base_report, income_insights, partner_insights) handle both user_token and user_id parameters. Frontend updated to display both user_token and user_id when available. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
- Add null checks for Java error body reading to prevent NullPointerException - Fix Java and Ruby to only retry on INVALID_FIELD errors, not all errors - Fix duplicate client_user_id generation: now reuses same ID on retry across all backends - Remove superfluous comments for cleaner, self-documenting code 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Changed all instances of itemID to itemId to follow Java camelCase convention consistently with other variables like userId, accessToken, etc. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
The compiled go/server binary (22MB) should not be tracked in git. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
- Node.js: 40.0.0 → 41.0.0 - Python: 37.1.0 → 38.0.0 - Go: 40.1.0 → 41.0.0 (updated import path from v40 to v41) - Java: 38.1.0 → 39.0.0 - Ruby: 44.1.0 → 45.0.0 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This reverts commit 629693f.
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.
update quickstart to support new user apis