We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We use the proper expanded counts for expansion fields:
reso-certification-etl/lib/process-data-availability.js
Line 242 in a02515a
Line 393 in a02515a
We should be using count that is calculated based on whether the field is an expansion or not:
count
Line 241 in a02515a
cc: @darnjo
The text was updated successfully, but these errors were encountered:
#56: update tests
d590d35
#56: update with proper expansion counts
7e319e6
#56: Update availability percentage calculation for expansion lookups (…
461fdbc
…#57) * #56: update tests * #56: update with proper expansion counts
mohit-s96
Successfully merging a pull request may close this issue.
We use the proper expanded counts for expansion fields:
reso-certification-etl/lib/process-data-availability.js
Line 242 in a02515a
but this needs to be updated for the expansion lookups as well:
reso-certification-etl/lib/process-data-availability.js
Line 393 in a02515a
We should be using
count
that is calculated based on whether the field is an expansion or not:reso-certification-etl/lib/process-data-availability.js
Line 241 in a02515a
cc: @darnjo
The text was updated successfully, but these errors were encountered: