Skip to content
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

Object names from ftrack initially sync to AYON lacking flanking underscore/s #137

Open
2 tasks done
ryanzujic opened this issue Sep 18, 2024 · 3 comments
Open
2 tasks done
Labels
community Issues and PRs coming from the community members

Comments

@ryanzujic
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior:

Thanks for everyone's efforts on this great toolset so far.

There appears to be an issue when folders or tasks are created on ftrack with flanking underscore/s. When this appears in AYON, it is without the flanking underscores. If the object is later renamed in ftrack, the name updates to match the new name exactly (ie, including any leading and trailing underscores present).

Initial sync:

image

image

After renaming:

image

image

Expected Behavior:

The folder or task name synced to AYON should be consistent across update scenarios. If underscores are deliberately stripped, then that should be consistent. Ideally, the name should be retained as written in FTrack (including underscores).

Version

1.0.0

What platform you are running on?

Windows, Linux / Ubuntu

Steps To Reproduce:

Create a folder or task on ftrack named with a leading and/or trailing underscore/s. Save and observe how it appears on the local AYON server.

We are using ayon-ftrack 1.2.0.

Are there any labels you wish to add?

  • I have added the relevant labels to the bug report.

Relevant log output:

No response

Additional context:

This is a test project to determine the robustness and limitations of the FTrack AYON integration. We would obviously love to see true syncing between AYON and FTrack to improve its suitability for tracking large ongoing productions.

Thank you!

@iLLiCiTiT
Copy link
Member

I'm afraid that AYON does not allow this naming convention.

@ryanzujic
Copy link
Author

Good to know, thank you. If the naming convention isn’t allowed, should renaming events be handled with the same cleanup steps so this can’t slip through?

@iLLiCiTiT
Copy link
Member

I "think" you're partially right. Because it will change label but name is still without underscores.

@m-u-r-p-h-y m-u-r-p-h-y added the community Issues and PRs coming from the community members label Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community Issues and PRs coming from the community members
Projects
None yet
Development

No branches or pull requests

3 participants