API for managing project–organisation relationships#55
Open
LabibaVIC wants to merge 7 commits into
Open
Conversation
LabibaVIC
changed the title
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
1 participant
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.
This PR introduces an API for managing relationships between projects and organisations.
It includes:
Create relationship between project and organisation
Fetch all project–organisation relationships
Duplicate relationship prevention at application level
Safe handling of Prisma foreign key constraints
Consistent API response structure across endpoints
Improvements
Implemented duplicate prevention for relationships before insertion
Added structured error handling using try/catch blocks
Handled Prisma constraint errors safely
Ensured consistent response format across endpoints
Testing
Verified successful creation of relationship using POST endpoint
Verified duplicate prevention works as expected
Verified GET endpoint returns all relationships correctly
Confirmed API handles invalid requests without crashing server