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

Convert addon for new ayon core #2

Merged
merged 8 commits into from
Apr 10, 2024
Merged

Conversation

iLLiCiTiT
Copy link
Member

Description

Changes related to 0.3.0 release of ayon core. All changes happened in client code.

Additional information

Use ayon_core over openpype.

Testing notes

  1. Create addon package.
  2. Upload to server.
  3. Use the addon version in bundle.
  4. Test logic of OpenRV (I don't know how...).

@iLLiCiTiT iLLiCiTiT requested a review from kalisp April 9, 2024 13:20
Comment on lines 19 to +20
if frame_start is None or frame_end is None:
log.warning("No edit information found for {}".format(asset_name))
log.warning("No edit information found for {}".format(folder_path))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As far as I know folder entities in AYON always have attrib.frameStart and attrib.frameEnd. When it does not that would be considered a bug in the backend? Right? If that's ensured to exist always on a folder then maybe this is None check can be removed?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will do with task entity PR :)

Comment on lines +12 to +14
folder_entity = get_current_folder_entity(fields={"path", "attrib"})
folder_path = folder_entity["path"]
folder_attribs = folder_entity["attrib"]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since AYON core refactoring many other DCCs swapped this out with using the attributes from the Task Entity instead. Should this as well? get_current_task_entity?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wanted, but then I was like: That should be different PR, it can be in changelog.

@kalisp kalisp assigned iLLiCiTiT and unassigned kalisp Apr 10, 2024
@iLLiCiTiT iLLiCiTiT merged commit 1a44ed6 into develop Apr 10, 2024
@iLLiCiTiT iLLiCiTiT deleted the enhancement/use-new-ayon-core branch April 10, 2024 10:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants