Removes unnecessary project fragment for project level packages query
@10io quoted
I was looking at the packages list page (project level) for a community MR review and I had to look at the GraphQL query that we execute for the packages list. I'm having hard time understanding why we query:
project { id name fullPath webUrl }
? I'm assuming that these fields are for the packages list at the group level but for the project level, couldn't we simply skip asking these? At the project level, on a page with 20 packages, we're going to return 20 times the exact same structure, so we might as well multiplex the packages list query with a project query that will bring this structure = the structure is returned only once. Am I missing something?
Solution
The project fragment is required only for group level packages query.
Edited by Rahul Chanila