Open
Conversation
❌ Deploy Preview for roaring-ganache-c7465f failed. Why did it fail? →
|
Collaborator
|
pls resolve conflicts @navin-oss .which issue does this close? |
Nitya-003
requested changes
Mar 7, 2026
Owner
Nitya-003
left a comment
There was a problem hiding this comment.
@navin-oss Please mention the issue number and resolve the conflicts.
Collaborator
|
@navin-oss pls resolve conflicts and site the issue it addresses.apertre is ending soon. |
cb0f243 to
e59c874
Compare
Contributor
Author
|
Hi @Nitya-003, |
Owner
|
@navin-oss You can have your time. and check conflicts on your other PRs too. |
Collaborator
|
@navin-oss pls check this asap |
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
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 backend data store confusion by removing the deprecated in-memory store:
Changes Made:
backend/models/BatchStore.js- The unused in-memory store that was causing architectural confusionAnalysis:
The backend had two data stores:
Batch.js- The primary data store used by all routes inserver.jsBatchStore.js- An unused Map-based store initialized with sample data that was never imported anywhere in the codebaseThe
BatchStore.jsfile contained:CROP-2024-001)All routes in
server.jscorrectly use MongoDB via theBatchmodel (see lines 320-536), so removing this unused file eliminates the confusion without affecting functionality.Branch pushed:
fix/architectureCommit:
59b2853- fix: remove deprecated BatchStore.js to eliminate data store confusion