-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add methods for handling JSON #33
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #33 +/- ##
==========================================
Coverage 100.00% 100.00%
==========================================
Files 8 9 +1
Lines 530 656 +126
==========================================
+ Hits 530 656 +126
|
) -> tuple[str, str]: | ||
"""Internal function to extract metadata from json files | ||
|
||
Note: Slicer version is not currently included in the json file |
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.
Note: This is perhaps another argument for dropping slicer_version
from AfidSet
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.
Yes, I agree - if we end up dropping this, I would prefer to do it in a separate PR
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.
A couple of pretty minor things -- this largely looks good
Currently returning the slicer_version as "unknown" as the version is not currently specified in the .json file outputted from the slicer markup json.
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.
One adjustment to the type hints then feel free to merge
Proposed changes
Closes #17 by adding in the necessary methods and tests for handling JSON associated fiducials. Also took the opportunity to update some existing docstrings and names of fcsv associated tests.
NOTE: This one should be reviewed and merged after #37, as it has been rebased to account for the coordinate system conventions
Types of changes
What types of changes does your code introduce? Put an
x
in the boxes that applyChecklist
Put an
x
in the boxes that apply. You can also fill these out after creating the PR. If you are unsure about any of the choices, don't hesitate to ask!poe quality
taskNotes
All PRs will undergo the unit testing before being reviewed. You may be requested to explain or make additional changes before the PR is accepted.