Geo: Implement state machine on a state model (Refactoring)
What does this MR do and why?
We store verification status in a separate table but we define the state machine in the main model. This is confusing and it even led to a bug because the main model record has not to be touched when the status is updated. This MR moved state machine definition to a separate concern. This MR fixes the mentioned bug as a side-effect and it doesn't target it directly.
Screenshots or screen recordings
These are strongly recommended to assist reviewers and reduce the time to merge your change.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Valery Sizov