Skip to content

Conversation

@jmesnil
Copy link
Collaborator

@jmesnil jmesnil commented Jan 6, 2026

Failure is reported in the TCK by the tests/optional/features/test_invalid_business_logic.py::test_missing_required_message_fields test.

@jmesnil jmesnil added this to the 1.0.0 milestone Jan 6, 2026
@kabir
Copy link
Collaborator

kabir commented Jan 6, 2026

I also saw this error, and was planning on working on it this morning. I think the TCK looks for an InvalidParamsError, so we need the mapper to throw that somehow

EDIT: nm, I see you have changed the mapper :-)

@Named("requireNonEmpty")
default String requireNonEmpty(String value) {
if (value == null || value.isEmpty()) {
throw new IllegalArgumentException("Required field cannot be null or empty");
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should be InvalidParamsError since that is what the TCK tests for

Failure is reported in the TCK by the tests/optional/features/test_invalid_business_logic.py::test_missing_required_message_fields test.

Signed-off-by: Jeff Mesnil <[email protected]>
@kabir kabir merged commit f4af6a3 into a2aproject:main Jan 6, 2026
9 of 19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants