Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Inventory unexpectedly marked as Low Stock #772

Closed
wants to merge 4 commits into from
Closed

fix: Inventory unexpectedly marked as Low Stock #772

wants to merge 4 commits into from

Conversation

sainak
Copy link
Member

@sainak sainak commented May 20, 2022

If the FacilityInventoryMinQuantity object is not present for an item it uses the value defined in the FacilityInventoryItem
so the fix would be to ignore the min value in FacilityInventoryItem and retire the min_quantity field

#725, ohcnetwork/care_fe#2437

@sainak sainak requested a review from a team as a code owner May 20, 2022 18:53
@vigneshhari
Copy link
Member

@sainak the min_quantity can stay and maybe FE can ignore the flag if the min_quantity value is not present, or we can add that logic into our flagging system.

@sainak
Copy link
Member Author

sainak commented May 22, 2022

@sainak the min_quantity can stay and maybe FE can ignore the flag if the min_quantity value is not present, or we can add that logic into our flagging system.

Sure I'll apply the changes

@vigneshhari
Copy link
Member

@sainak in FE or BE ?

@sainak
Copy link
Member Author

sainak commented May 22, 2022

Its possible to do it on the BE but the min_quantity will still be redundant atlest in FacilityInventoryLogSerializer

@sainak
Copy link
Member Author

sainak commented May 22, 2022

@vigneshhari we can also rename the min_quantity field to default_min_quantity in the response and decide the is_low based on the FacilityInventoryMinQuantity

@vigneshhari
Copy link
Member

yea sure

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants