-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
chore: split the SDKConnect class into smaller chunks and add unit tests #8028
chore: split the SDKConnect class into smaller chunks and add unit tests #8028
Conversation
…to-SDKConnect-handlers
…to-SDKConnect-handlers
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
…_split-the-SDKConnect-class-into-smaller-chunks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…_split-the-SDKConnect-class-into-smaller-chunks
…'[object global]' error
No top level dependency changes detected. Learn more about Socket for GitHub ↗︎ |
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat is new author?A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package. Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
…to-SDKConnect-handlers
…_split-the-SDKConnect-class-into-smaller-chunks
The base branch was changed.
…nnect-class-into-smaller-chunks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Kudos, SonarCloud Quality Gate passed! |
Tiny tiny detail that may have come from a different branch. The Screen.Recording.2023-12-12.at.17.05.04.movSteps:
Expected result: Actual result: |
Since the bug reported doesn't break the overall functionality and is of low severity this is going to merged and #8079 was opened. |
Description
Split the SDKConnect class into smaller chunks to make the code more testable and add unit tests.
Related issues
Fixes:
Manual testing steps
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist