-
Notifications
You must be signed in to change notification settings - Fork 24
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: filenameExists
Validation Rule
#1456
base: develop
Are you sure you want to change the base?
Conversation
f69406c
to
4c9551d
Compare
filenameExists
Validation Rule
3cce7de
to
3451b65
Compare
Quality Gate passedIssues Measures |
where_clauses: Optional[list] = None, | ||
): | ||
# if the ValidateAttribute object already has a SynapseStorage object, just requery the fileview, if not then login | ||
if hasattr(self, "synStore"): |
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.
Under what situations that the if statement here: if hasattr(self, "synStore")
would get triggered?
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.
If the ValidateAttribute
object already has a synStore
attribute because it was used during the validation of another column
This PR introduces the
filenameExists
metadata validation rule that checks for parity between the file paths in a metadata manifest (and the associated entityIds) and the file paths in the master file view on Synapse.Another associated change is that schematic's handling of paths for all files on synapse has been changed; paths now include the project name at the beginning of the path to match the format of paths in synapse file views.