implemented project level user pins - #1275
Conversation
GitLab Pipeline ActionGeneral informationLink to pipeline: https://gitlab.com/code0-tech/development/sagittarius/-/pipelines/2841077477 Status: Failed Job summariesrspec: [cloud]Coverage report available at https://code0-tech.gitlab.io/-/development/sagittarius/-/jobs/16449108757/artifacts/tmp/coverage/index.html rspec: [ee]Coverage report available at https://code0-tech.gitlab.io/-/development/sagittarius/-/jobs/16449108756/artifacts/tmp/coverage/index.html rspec: [ce]Coverage report available at https://code0-tech.gitlab.io/-/development/sagittarius/-/jobs/16449108755/artifacts/tmp/coverage/index.html docs:previewDocumentation preview available at https://code0-tech.gitlab.io/-/development/telescopium/-/jobs/16449222873/artifacts/out/index.html rubocop1071 files inspected, no offenses detected |
nicosammito
left a comment
There was a problem hiding this comment.
I thought about the current implementation. remove the namespacePins and projectPins from the User Object. Add a pinned property to Namespace and NamespaceProject. It should be user depended. Make sure you also adjust the mutation for pinning NamespaceProjects because this is linked to a Namespace
3ab40a8 to
5e58a7f
Compare
I would disagree with that. If you think about the data graph, the pinned namespaces and projects belong to a user. The namespace or project doesn't care whether it is pinned or not. |
Completely forgot about this. Okay then, the projectPins just need to be linked to a Namespace. So adjust the usersUpdateProjectPins mutation and the User.projectPins field |
Resolves: #557