Bb2 4376 v3 changes #79
Merged
+67
−23
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
jimmyfagan
reviewed
Jan 21, 2026
Comment on lines
+147
to
+148
| yarn build | ||
| yarn build:types |
Contributor
There was a problem hiding this comment.
We should probably wrap this with `blah` or ```blah``` to match formatting from other sections and make this easier to read.
Co-authored-by: jimmyfagan <90421499+jimmyfagan@users.noreply.github.com>
jimmyfagan
approved these changes
Jan 21, 2026
Contributor
jimmyfagan
left a comment
jimmyfagan
left a comment
There was a problem hiding this comment.
Worked for me, approved!
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.
Changes to allow for v3 token exchange to function properly
JIRA Ticket:
BB2-4376
What Does This PR Do?
Allows for v3 functionality to work on the sample clients. Also includes more instructions in the README-sdk dev document to facilitate a better CMS developer experience.
What Should Reviewers Watch For?
Any areas of breaking functionality or any places where the added instructions for local setup is unclear. It is not the most straightforward process as is.
Validation
Validated with local run of auth flow
What Security Implications Does This PR Have?
Please indicate if this PR does any of the following: