You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
JIRA Ticket: BB2-3798
Update readme text related to scope checking under Smart App v2 scopes (vs legacy scopes)
What Does This PR Do?
Updated readme text related to scope checking under Smart App v2 scopes (vs legacy scopes)
What Should Reviewers Watch For?
If you're reviewing this PR, please check for these things in particular:
Validation
Check the readme is accurate w.r.t access token scopes usage (SMART App v2 scopes)
and optionally, verify that the SDK works with the client code - BB2 Node Sample App:
JFU-NAVA-PBC
changed the title
jimfuqian/BB2-3798 Update readme scopes related text to reflect smart app v2 scopes
jimfuqian/BB2-3798 Update readme to reflect smart app v2 scopes
Apr 30, 2025
JFU-NAVA-PBC
changed the title
jimfuqian/BB2-3798 Update readme to reflect smart app v2 scopes
jimfuqian/BB2-3798 Update readme to reflect smart app v2 scope usage
Apr 30, 2025
The last two commits here changed a bunch of files, can you say a bit about what that doc regen was, how you ran it, and why it was needed? Should those files be put in a .gitignore or something instead of having to add manual steps to keep them updated?
The last two commits here changed a bunch of files, can you say a bit about what that doc regen was, how you ran it, and why it was needed? Should those files be put in a .gitignore or something instead of having to add manual steps to keep them updated?
sdk javascript source is annotated at methods and classes level - like javadoc for java codes, it provides more details beyond readme, it is surposedly direct consume from the source tree without going into the source code, and it is hierarchically organized for easy drill down, e.g. I wanted to see what are in AuthorizationToken...
note,
it is not packaged with the sdk tarball.
it common practice for node project and good to keep...
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
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.
JIRA Ticket:
BB2-3798
Update readme text related to scope checking under Smart App v2 scopes (vs legacy scopes)
What Does This PR Do?
Updated readme text related to scope checking under Smart App v2 scopes (vs legacy scopes)
What Should Reviewers Watch For?
If you're reviewing this PR, please check for these things in particular:
Validation
Check the readme is accurate w.r.t access token scopes usage (SMART App v2 scopes)
and optionally, verify that the SDK works with the client code - BB2 Node Sample App:
CMSgov/bluebutton-sample-client-nodejs-react#69
What Security Implications Does This PR Have?
Please indicate if this PR does any of the following: