-
Notifications
You must be signed in to change notification settings - Fork 9
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
Fix bug where custom project code field wasn't being used on sync from Ayon to SG #67
Conversation
That would probably work, we'd need to change the function to remove the leading |
Yeah I had the same thought, let's leave it like this then |
…ome typos on logging
@@ -43,8 +43,6 @@ def _sg_to_ay_dict(sg_entity: dict, project_code_field=None) -> dict: | |||
|
|||
if not label and not task_type: | |||
raise ValueError(f"Unable to parse Task {sg_entity}") | |||
else: |
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.
@Minkiu this was overriding the label every time
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.
Here I though I was playing it safe... 🤦 thanks!
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.
Thanks for the contribution, merging!
@@ -162,7 +162,6 @@ def start_processing(self): | |||
self.sg_url, | |||
self.sg_script_name, | |||
self.sg_api_key, | |||
project_code_field=self.sg_project_code_field, |
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.
Might as well delete it from line 45
since we are not using it any more, and we trust that it comes with the payload...
@@ -43,8 +43,6 @@ def _sg_to_ay_dict(sg_entity: dict, project_code_field=None) -> dict: | |||
|
|||
if not label and not task_type: | |||
raise ValueError(f"Unable to parse Task {sg_entity}") | |||
else: |
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.
Here I though I was playing it safe... 🤦 thanks!
The custom project code field was missing on this call:
Although perhaps better than querying the
sg_project
again the best would be to append the existingsg_project
variable that already exists on the function and contains the project code field, something like:@Minkiu thoughts?