Open
Conversation
antirotor
requested changes
Mar 19, 2026
Member
There was a problem hiding this comment.
I think it fixed the problem where the returned data were wrong, but there is still discrepancy between the data fields returned.
So lets assume one project TestProject and running these two calls:
import ayon_api
from pprint import pprint
project_name = "TestProject"
graphql_result = ayon_api.get_project(project_name, fields={"attrib"})
rest_result = ayon_api.get_rest_project(project_name)
key_diff = set(graphl_result["attrib"].keys()) - set(rest_result["attrib"].keys())in my case, the key_diff is:
{'ftrackId', 'shotgridPush', 'shotgridType', 'tools', 'shotgridId', 'ftrackPath'}
other than that the values are matching.
I think those two call should produce 1:1 result.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changelog Description
Fetch correct project using GraphQl and fill more data when merging GraphQl and REST project data.
Additional review information
When GraphQl was used to get project it did not use project name as filter for the project which lead to use "first" project -> wrong data.
Merge of GraphQl and REST data was restricted to specific keys, now the restricted keys will override anything from REST but all other keys from GraphQl are appended to the REST project.
Testing notes:
get_projectshould work if only graphql fields are requested (e.g.fields={"attrib"}).