Validate API configuration requests against the database schema - #71
Merged
Conversation
Duslerke
reviewed
Aug 10, 2026
…Recorded the endpoint count Also Confirmed the count increases by exactly one afterward.
Duslerke
approved these changes
Aug 14, 2026
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
2 participants
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.
What changed
404 Not Foundwhen the parent API does not exist.Why
Missing values could reach the data-access code and result in a
500 Internal Server Error. The API now rejects invalid requests with an appropriate client response.The validation follows the existing PostgreSQL schema without introducing unsupported limits for fields stored as
text.Testing