Fix project creation permissions using creatorHatIds #9
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.
Summary
creatorHatIdsfrom TaskManager subgraph entity to check project creation permissionProblem
The TaskManager has TWO permission levels that were being conflated:
creatorHatIds(TaskManager-level): Who can CREATE PROJECTSrolePermProj(Project-level): Who can CREATE/CLAIM/REVIEW/ASSIGN TASKSChanges
queries.jscreatorHatIdsto GraphQL queriesPOContext.jscreatorHatIdsfrom taskManagerProjectSidebar.jscreatorHatIdsfor canManageProjects checkMainLayout.jsroleHatIdswhen creating projects for default permissionsTaskColumn.jsrolePermissionsfor task operationspermissions.jsErrorParser.jsDependencies
Requires subgraph PR to be merged first:
PerpetualOrganizationArchitect/subgraph-pop#24
Test plan
🤖 Generated with Claude Code