-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
✨CAT: add test_primary_keys_data_type
#38755
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
Looks good to me! I wonder how many connectors would fail this 👀
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.
small comment, but nothing blocking. looks good to me
@@ -83,6 +83,7 @@ class DiscoveryTestConfig(BaseConfig): | |||
backward_compatibility_tests_config: BackwardCompatibilityTestsConfig = Field( | |||
description="Configuration for the backward compatibility tests.", default=BackwardCompatibilityTestsConfig() | |||
) | |||
skip_primary_keys_data_type_validation: Optional[bool] = Field(False, description="Skip primary keys data type validation") |
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.
Is there a reason why we made this one skip...
? To make things more consistent, could we instead make this validate_primary_key_data_type
and default to True.
Co-authored-by: Serhii Lazebnyi <serhii.lazebnyi@globallogic.com>
What
Resolves:
How
TestDiscovery.test_primary_keys_data_type
, which validates that primary keys are not of typearray
orobject
validate_primary_keys_data_type
toTestBasicRead.test_read
, which validates that primary keys are not of typearray
orobject
in records and ensures that at least one primary key is non-null when there is a composite primary keyReview guide
tests/test_core.py
unit_tests/test_core.py
User Impact
No user impact
Can this PR be safely reverted and rolled back?