-
Notifications
You must be signed in to change notification settings - Fork 6
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
FT-843: Implement GET operation that takes a list of attributes and relationships #458
Conversation
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.
Good progress!
Here are a few minor changes:
…h support for when attributes or relationships_attributes are present
Added by mistake
…o maintain consistency
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!
Make sure when writing integration tests to check real-world scenarios (which I later fixed in my latest commits) ✅
For example, in your previous integration tests, you only tested for [attributes=["name", "qualified_name"]
which misses cases for 🧪
related_attributes
attributes
(usingAtlanField
)related_attributes
(usingAtlanField
)
Breaking Change:
ignore_relationships = False
toignore_relationships = True
Features:
attribute
andrelationships_attributes
params inAssetClient.get_by_qualified_name()
andAssetClient.get_by_guid()
which usesfluent search
and not the default raw api call