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

Resolve #304: Introduce state machine approach #187

Merged
merged 29 commits into from
Aug 18, 2022

Conversation

saalistaja
Copy link
Contributor

@saalistaja saalistaja commented Apr 25, 2022

  • Refactored previous approach to spring state machine
  • Mapped current phase, status to new onboarding state enums
  • Transitions triggered by simple events from controllers and one technical event for auto-transition on status check

@saalistaja saalistaja changed the title Introduce state machine approach Resolve #304: Introduce state machine approach Aug 16, 2022
Lukas Lukovsky added 3 commits August 16, 2022 15:15
Adapt document verification tests to the latest changes
- Mark as choice state PRESENCE_CHECK_FAILED and PRESENCE_CHECK_REJECTED
@saalistaja saalistaja marked this pull request as ready for review August 17, 2022 09:23
@saalistaja saalistaja requested a review from romanstrobl August 17, 2022 09:47
Copy link
Member

@romanstrobl romanstrobl left a comment

Choose a reason for hiding this comment

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

In general, these changes are exactly what we needed to improve the state handling in the application. I found several minor issues which are related to consistency, several minor performance improvements and ideas. Feel free to ignore if you disagree with proposed changes.

jsonSerializationService.deserialize(identityVerification.getSessionInfo(), SessionInfo.class);
if (sessionInfo == null) {
logger.error("Checking presence verification failed due to invalid session info, {}", ownerId);
identityVerification.setErrorDetail("Unable to deserialize session info");
Copy link
Member

Choose a reason for hiding this comment

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

Just a note to myself, we'll need to also add the error origin due to parallel pull request: #315

@saalistaja
Copy link
Contributor Author

@romanstrobl Thanks for the feedback. I have fixed all the found issues.
Let's merge and continue later with an advanced state machine evolution.

@saalistaja saalistaja merged commit 0940e8f into develop Aug 18, 2022
@saalistaja saalistaja deleted the state-machine-approach branch August 18, 2022 16:44
saalistaja added a commit that referenced this pull request Aug 19, 2022
- Refactored previous approach to spring state machine
- Mapped current phase, status to new onboarding state enums
- Transitions triggered by simple events from controllers and one technical event for auto-transition on status check
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