Skip to content

Chore: Add status scope support #188

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

Merged
merged 7 commits into from
Oct 14, 2024

Conversation

iLLiCiTiT
Copy link
Member

@iLLiCiTiT iLLiCiTiT commented Oct 9, 2024

Changelog Description

Added base support for scope of statuses.

Additional info

Scope is auto-filled for project which does not have filled scope in statuses, this should allow backwards compatibility even for servers that are not yet 1.5.0 .

Entity hub also supports scope on statuses. Added validation of statuses based on the scope. Scope is auto-filled on load and removed on save if server does not support it yet.

Testing notes:

  1. Using ayon api on AYON server 1.4.2 and lower should still work as before. Project statuses already contain scope. Entity hub can update statuses in project anatomy, and can set statuses on entities.
  2. Using ayon api on current develop of AYON server (or 1.5.0 if is already released) should already support the scope on statuses and entity hub should be able to change scope of statuses on project.

Resolves #183

@iLLiCiTiT iLLiCiTiT added the type: enhancement New feature or request label Oct 9, 2024
@iLLiCiTiT iLLiCiTiT self-assigned this Oct 9, 2024
Copy link
Member

@kalisp kalisp left a comment

Choose a reason for hiding this comment

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

Not sure how to test this, I used this PR on 1.5.1+202410141053 and published fine, tested on 1.4.2+202409231943 (Nuke, Maya..) and it didn't explode.

@iLLiCiTiT iLLiCiTiT merged commit 40dc4ae into develop Oct 14, 2024
2 checks passed
@iLLiCiTiT iLLiCiTiT deleted the enhancement/auto-fill-status-scope branch October 14, 2024 10:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add support for status per entity type
2 participants