Skip to content

Conversation

@MrCreosote
Copy link
Member

All the other changes in this PR flow out of that single change. eesh.

TODO: test the UITokens for MFA status once it's exposed in the API layer.

Turning whitespace off makes the review a lot simpler

All the other changes in this PR flow out of that single change. eesh.

TODO: test the UITokens for MFA status once it's exposed in the API layer.
@MrCreosote MrCreosote requested a review from dauglyon November 18, 2025 22:19
@codecov
Copy link

codecov bot commented Nov 18, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.42%. Comparing base (4b0e4d2) to head (d2a68a6).
⚠️ Report is 7 commits behind head on develop.

Additional details and impacted files
@@            Coverage Diff             @@
##             develop     #503   +/-   ##
==========================================
  Coverage      93.41%   93.42%           
- Complexity      2167     2169    +2     
==========================================
  Files            129      129           
  Lines           7626     7636   +10     
  Branches        1181     1184    +3     
==========================================
+ Hits            7124     7134   +10     
  Misses           459      459           
  Partials          43       43           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

assertThat("incorrect state", ti.getOAuth2State(), is(ES));
assertThat("incorrect pkce", ti.getPKCECodeVerifier(), is(ES));
assertThat("incorrect user", ti.getUser(), is(Optional.empty()));
assertThat("incorrect user", ti.getUser(), is(opt()));
Copy link
Collaborator

Choose a reason for hiding this comment

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

I would not immediately know opt() vs Optional.empty meant an empty optional, but I also am not steeped in Java norms.

Copy link
Member Author

@MrCreosote MrCreosote Nov 18, 2025

Choose a reason for hiding this comment

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

Yeah, it's just personal short hand since it's used over and over in these tests

Copy link
Collaborator

@dauglyon dauglyon left a comment

Choose a reason for hiding this comment

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

The test changes seem good, I didn't see anything unexpected except the test looping logic but that makes sense. Non-test changes are as expected. Not sure about the LoginState comment but assume it's a good idea given mfa state is indeed a type of login state. Should be good to merge!

@MrCreosote
Copy link
Member Author

The login state is just referring to the endpoint where the user gets to choose what account to log into (or for KBase, affirms they're logging into the right account. As such, MFA status doesn't really matter unless we wanted to stop the login flow right there or something

@MrCreosote MrCreosote merged commit 3d6f50a into develop Nov 19, 2025
12 checks passed
@MrCreosote
Copy link
Member Author

It doesn't hurt to have it though, could be used to give feedback to the user that their MFA state is as expected (or not)

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.

3 participants