-
Notifications
You must be signed in to change notification settings - Fork 20
feat(api): validate request fields before rpc calls #497
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
prdai
wants to merge
4
commits into
LDFLK:main
Choose a base branch
from
prdai-archive:fix/344-pre-rpc-field-validation
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 3 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
f7b60db
feat(api): validate request fields before rpc calls
prdai 08316b9
chore: drop issue url from validation comments
prdai 08c45e0
chore: drop issue references from validation comments
prdai ca68941
fix(api): reject blank dates and array entries missing keys
prdai File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Reject invalid calendar and clock values.
These patterns accept invalid values such as
2025-02-30and2025-01-01T29:99Z. Such values pass request validation and reach the gRPC layer, instead of producing HTTP 400 as required.Use calendar-aware date-time parsing after the lexical format check.
opengin/ingestion-api/update_api_service_copy.bal#L49-L50: validate optional date-time values semantically.opengin/ingestion-api/update_api_service_copy.bal#L78-L79: validatecreatedsemantically.opengin/ingestion-api/update_api_service_copy.bal#L100-L101: validate relationshipstartTimesemantically.opengin/ingestion-api/update_api_service_copy.bal#L121-L122: validate attributestartTimesemantically.📍 Affects 1 file
opengin/ingestion-api/update_api_service_copy.bal#L49-L50(this comment)opengin/ingestion-api/update_api_service_copy.bal#L78-L79opengin/ingestion-api/update_api_service_copy.bal#L100-L101opengin/ingestion-api/update_api_service_copy.bal#L121-L122🤖 Prompt for AI Agents