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

Rethink about minimum needs behaviour #3610

Closed
lucernae opened this issue Jan 17, 2017 · 1 comment
Closed

Rethink about minimum needs behaviour #3610

lucernae opened this issue Jan 17, 2017 · 1 comment
Assignees

Comments

@lucernae
Copy link
Collaborator

lucernae commented Jan 17, 2017

Right now we had several issues:

Problem

  • Minimum needs is calculated pretty much like post processors but it is being defined as ResourceParameter
  • Minimum needs have additional informations such as unit, but post processor does not. It is possible to add unit key in the field or in post processors
  • Minimum needs can be configured by user. This makes their post processor needs to be created dynamically. But there are some minimum needs that is hardcoded such as hygiene packs and additional rice for pregnant woman. There is an ugly mix of having to nicely define post processors in definitions, or to have user able to configure it in minimum needs profile.
@lucernae lucernae added this to the Version 4.0 Final milestone Jan 17, 2017
@lucernae lucernae self-assigned this Jan 17, 2017
@lucernae
Copy link
Collaborator Author

Closing this.
These behaviour is accepted for now.

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

No branches or pull requests

1 participant