feat(contracts): implement centralized contract lifecycle state service - #167
Merged
Merged
Conversation
|
@AdeMi20 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What was done
A centralized contract state management service was built to provide a single, secure source of truth for contract lifecycle transitions. This involved creating a new database migration to expand the contract status ENUMs (adding draft, pending_funding, and submitted) and creating an audit logging table (contract_state_logs). The new ContractStateService enforces strict state machine rules so that contracts can only move between valid states (e.g., a contract cannot move directly from draft to active). Every successful state transition updates the database within a transaction, writes a detailed audit log entry, and immediately dispatches a customized notification to both the client and freelancer to keep them informed.
Close #150