Closed nevoodoo closed 2 months ago
@vivbak @illusional I have moved the ourdna
field to the GraphQLProject
type, and removed the nullable checks like was suggested, and there is a project permissions check being made by the layer so I have removed it from the schema level for now. Keen to hear what you think, I have tested to make sure the query works as intended locally :)
Attention: Patch coverage is 95.59585%
with 17 lines
in your changes missing coverage. Please review.
Project coverage is 77.83%. Comparing base (
ab809cd
) to head (dc98692
). Report is 6 commits behind head on dev.:exclamation: Current head dc98692 differs from pull request most recent head 36b48be
Please upload reports for the commit 36b48be to get more accurate results.
Files | Patch % | Lines |
---|---|---|
db/python/layers/ourdna/dashboard.py | 94.64% | 9 Missing :warning: |
api/graphql/schema.py | 73.91% | 6 Missing :warning: |
test/test_ourdna_dashboard.py | 98.79% | 2 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Description
This PR adds the backend logic that aggregates the data needed for the OurDNA Dashboard UI.
See: https://docs.google.com/spreadsheets/d/1crEwZhFMD-m0sO4TGm-8FcwsFxGhg_IIyPB5yH2O7Q0/edit?usp=sharing
Changes
db/python/layers/ourdna/dashboard.py
that controls the aggregation logic.api/graphql/schema.py
that would offer a new field to query this data from.