Skip to content
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

TRIB-102, return the username along with the user ID in connectOutgoingMessageDTO #165

Merged
merged 3 commits into from
Mar 20, 2024

Conversation

haxwell
Copy link
Contributor

@haxwell haxwell commented Mar 19, 2024

No description provided.

Copy link

codecov bot commented Mar 19, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 80.08%. Comparing base (9c4e45b) to head (69a2632).
Report is 1 commits behind head on feature/connect-page.

Additional details and impacted files
@@                    Coverage Diff                     @@
##             feature/connect-page     #165      +/-   ##
==========================================================
+ Coverage                   79.79%   80.08%   +0.29%     
- Complexity                    529      531       +2     
==========================================================
  Files                          77       77              
  Lines                        1638     1662      +24     
  Branches                      266      267       +1     
==========================================================
+ Hits                         1307     1331      +24     
  Misses                        295      295              
  Partials                       36       36              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@@ -112,21 +113,32 @@ public List<ConnectOutgoingMessageDTO> handleConnectionIntent(String connectionI
if (connectionIntent == "") {
rtn.add(ConnectOutgoingMessageDTO.builder()
.message("Please confirm that you wish to connect.")
.to(toBeConnectedWithUserId)
.to(UsernameDTO.builder()
.userId(requestingUserId)
Copy link
Collaborator

@mrsbluerose mrsbluerose Mar 19, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe when I first worked through this method, this message "Please confirm that you wish to connect" was going to the toBeConnectedWith user as a confirmation that they accept the connection. Is this actually for the requesting user?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, thank you. Good find. I've corrected it.

@haxwell haxwell merged commit 189a0d2 into feature/connect-page Mar 20, 2024
3 checks passed
@haxwell haxwell deleted the TRIB-102 branch March 20, 2024 09:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants