First draft specific headcount functions #202
Open
Conversation
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
Aeilert
added
Priority: 4-Low
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hi @tonyfujs
Here is the list of headcount functions I created in order to only calculate the headcount in pipapi. I'm not sure we actually we want this. But it could be relevant if we do something like /headcount, /gini etc. as separate endpoints. Having a set of HC specific endpoints is also relevant for /cp-charts and /cp-key-indicators where we only need the headcount, but actually calculate all stats.
This can used together with a modified version of
pipapi:::rg_pip()that usewbpip:::prod_compute_headcount()as the underlying function.Not urgent, and maybe something we don't want to add. But adding for reference and discussion.