-
Notifications
You must be signed in to change notification settings - Fork 0
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
Feature/pdct 1419 map family metadata to metadata key in family json structure #13
Merged
odrakes-cpr
merged 23 commits into
main
from
feature/pdct-1419-map-family-metadata-to-metadata-key-in-family-json-structure
Sep 9, 2024
Merged
Feature/pdct 1419 map family metadata to metadata key in family json structure #13
odrakes-cpr
merged 23 commits into
main
from
feature/pdct-1419-map-family-metadata-to-metadata-key-in-family-json-structure
Sep 9, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
checks if row has any required columns with empty values, checks if required columns from a row are missing
add tests accordingly
will revisit to try and fix pyright typing errors
- add function to check for value and key existence in nested objects - add private methods - doc string tidy ups - tidy up function that gets budget information
it can be used more widely across the codebase
instead of raising and stopping the tool from running we can just stdout the error
- remove the function that checks for values in nested objects - we don't want the tool to stop running for malformed data, only when a key is missing. - so we have updated the helper function to check for false/empty values in a list and just echo it out and then take it to the client - We have gone back to pythons normal way of accessing keys in a dict, where a key error will be raised if we try access something that is not there
katybaulch
reviewed
Sep 9, 2024
katybaulch
reviewed
Sep 9, 2024
katybaulch
reviewed
Sep 9, 2024
katybaulch
reviewed
Sep 9, 2024
katybaulch
reviewed
Sep 9, 2024
katybaulch
reviewed
Sep 9, 2024
katybaulch
reviewed
Sep 9, 2024
katybaulch
reviewed
Sep 9, 2024
katybaulch
reviewed
Sep 9, 2024
katybaulch
reviewed
Sep 9, 2024
katybaulch
reviewed
Sep 9, 2024
katybaulch
requested changes
Sep 9, 2024
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.
Great work! Just some small changes
katybaulch
approved these changes
Sep 9, 2024
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.
nice work!!
odrakes-cpr
deleted the
feature/pdct-1419-map-family-metadata-to-metadata-key-in-family-json-structure
branch
September 9, 2024 14:02
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What's changed?
Add functionality to the GCF data mapper tool; mapping family metadata from the source file to json output suitable for the bulk import tool
Proposed version
Please select the option below that is most relevant from the list below. This
will be used to generate the next tag version name during auto-tagging.
Visit the Semver website to understand the
difference between
MAJOR
,MINOR
, andPATCH
versions.Notes:
used -- e.g. Major > Minor > Patch
sure your selected option is marked
[x]
with no spaces in between thebrackets and the
x