i tried to write migrations, to remove existing zero-ltp allotment entries.
i give up :sob: .
mongoose + javascript async/await are a formidable foe, capable of ruining an average person's day simply by existing.
so for now, existing entries wont be deleted unless commit_ltp is called on them
Checklist:
[x] My commits are related to the pull request and look clean.
[ ] I have made mostly use of tailwind as many places as possible.
[x] I have added comments on any confusing or complex pieces of code.
yep perfectly fine like right now it's an issue bcoz data is already saved but in the new system if this happens at committing ltp time then it's perfectly fine.
closes #105, #84
Description
i tried to write migrations, to remove existing zero-ltp allotment entries. i give up :sob: . mongoose + javascript async/await are a formidable foe, capable of ruining an average person's day simply by existing.
so for now, existing entries wont be deleted unless
commit_ltp
is called on themChecklist: