-
Notifications
You must be signed in to change notification settings - Fork 78
[C API] Metadata schema field on tables #493
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
Conversation
|
@jeromekelleher You mentioned text dump round tripping - is that in python only? Couldn't see it in the C. |
Yep. Text support in C is strictly just for testing. Life is too short to write production quality text parsing in C! |
jeromekelleher
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM @benjeffery. Minor points above.
Codecov Report
@@ Coverage Diff @@
## master #493 +/- ##
==========================================
- Coverage 86.96% 86.84% -0.12%
==========================================
Files 21 21
Lines 15748 15944 +196
Branches 3066 3095 +29
==========================================
+ Hits 13695 13847 +152
- Misses 1034 1050 +16
- Partials 1019 1047 +28
Continue to review full report at Codecov.
|
|
LGTM, ready to copy-paste across many tables I think! |
ac97e66 to
4adfea5
Compare
|
@jeromekelleher I've given this another pass, after what we talked about with edge metadata. I've made |
jeromekelleher
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM @benjeffery, I'd say go for it. The NULL vs non-NULL thing is a bit philosophical when metadata_length == 0, so I think setting it to NULL on 0 is the right thing to do.
|
Ok, will copy across to other tables now. |
jeromekelleher
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM @benjeffery, just spotted a minor typo in the docs. Shall we merge this much and follow up with the Python tests?
d27fff3 to
363b49d
Compare
|
@jeromekelleher Squashed rebased and ready to merge (pending CI!). Yes, lets merge here as this is a natural break point as nothing is broken, just added. |
|
C lint has failed as azure is on its knees. I don't have permission to re-run it. |
I've been getting these errors a bit elsewhere too - tried rerunning them but they kept failing. |
|
I'll see if we can remove the dependency |
To split #491 up a bit I'm focusing on getting the C API right first.
Proof-of-concept for the python is done in #491 meaning I'm pretty sure this is the (per-table) changes we want. Only
individualsis modified for now. Once everyone is happy I'll do the other tables.I intend to do top-level (per tree sequence) metadata in another PR.