Closed dfalster closed 1 year ago
@ehwenk I suggest we address the other part of #725 issue (for long data) via a seperate branch and PR
@ehwenk I suggest we address the other part of #725 issue (for long data) via a seperate branch and PR
sure.
Patch coverage: 100.00
% and project coverage change: +0.03
:tada:
Comparison is base (
5fc970a
) 80.20% compared to head (e151a3d
) 80.24%.:exclamation: Current head e151a3d differs from pull request most recent head c099937. Consider uploading reports for the commit c099937 to get more accurate results
:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
Hi Lizzy,
Sorry but I don't understand what you were asking in your last message. You refer several times to "this" branch, but I suspect some of the this actually meant the one with the link?
In any case, perhaps two seperate commits is best?
Two commits is fine. There is a second branch where I made changes to metadata files and which had the initial changes for fixing entity_type that are now superceded. The other branch is: https://github.com/traitecoevo/austraits.build/tree/fix-entity_type-value_type-units-not-reading-in .
Solves first issue raised in #725, that entity_type and value_type are not being successfully read from a column of data.