fix: align batchService.js stage mapping with constants/stages.js#198
Merged
Nitya-003 merged 1 commit intoNitya-003:mainfrom Mar 15, 2026
Merged
fix: align batchService.js stage mapping with constants/stages.js#198Nitya-003 merged 1 commit intoNitya-003:mainfrom
Nitya-003 merged 1 commit intoNitya-003:mainfrom
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixed the stage inconsistency between
constants/stages.jsandbatchService.js.Issue: The stage mappings were completely different:
constants/stages.js:['farmer', 'mandi', 'transport', 'retailer']with mapping{ farmer: 0, mandi: 1, transport: 2, retailer: 3 }batchService.js:{ 'farmer': 0, 'processor': 1, 'distributor': 2, 'retailer': 3, 'consumer': 4 }(hardcoded inline)Fix applied:
STAGE_TO_NUMBERfromconstants/stages.jsSTAGE_TO_NUMBERThis now correctly matches the Solidity contract's
Stage enum(Farmer=0, Mandi=1, Transport=2, Retailer=3), preventing blockchain sync failures.