fix: handle empty string values in datetime parameters #443
Conversation
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
…ues tool failing with Invalid datetime for since error - Add enhanced validation for empty strings and whitespace - Apply consistent datetime validation across notifications.go - Improve parseISOTimestamp function with better error messages
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes list_issues tool failing with Invalid datetime for since error when AI SDKs pass empty strings for optional datetime parameters. Enhanced validation for empty strings and whitespace, applied consistent datetime validation across notifications.go, and improved parseISOTimestamp function with better error messages. Resolves issue where AI SDKs passing empty strings for optional datetime parameters would cause validation errors instead of being treated as unset parameters.