-
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
feat: JIRA 1818 - Adding Types to Lineage Response for Special Queries in Prov-API. #38
Conversation
Can you create a test for this feature? I'd like to run the test using pytest to verify the feature functionality. |
i also tried
|
Okay, I have added two small tests within the test_provenance_workflow section. I don't think this deserves a completely new test, as it can be checked elsewhere, where the special queries are being used and for efficiency purposes. |
I have fixed this issue. It seems I over-engineered my initial approach, as I was converting into a dictionary and then back into a pydantic object, hence the issue of object has no attribute 'get' |
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality.
|
Looking better now! I was able to get my environment configured and able to run adhoc.py. A use case that I wanted to test was the ability to list all datasets. Some suggested tweak to e.g.
|
I have added this now. |
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.
This provides client functionality to type returned graph response from the provena API. Working well and able to filter subtypes now more easily.
Jira-1818 (Minor): Adding Types to Lineage Response for Special Queries in Prov-API.
JIRA Ticket 1818
Checklist
Description
This ticket involves making the Lineage Response more type-friendly and robust, so users can easily access the properties of the response via type hints.
Notes for reviewer
This approach essentially allows you to access the LineageResponse in a typed manner. E.g.
response.graph.nodes
,response.graph.direction
etc