Skip to content

Fix strict mode validation for nested container expressions and generic types#1236

Closed
Chanwon-Seo wants to merge 8 commits intonaver:mainfrom
Chanwon-Seo:fix-strict-mode-nested-list
Closed

Fix strict mode validation for nested container expressions and generic types#1236
Chanwon-Seo wants to merge 8 commits intonaver:mainfrom
Chanwon-Seo:fix-strict-mode-nested-list

Conversation

@Chanwon-Seo
Copy link
Contributor

@Chanwon-Seo Chanwon-Seo commented Sep 4, 2025

Summary

Fixes strict mode validation for nested container expressions and generic types by ensuring correct type propagation.

Fixes #1234

(Optional): Description

Ensured AnnotatedType is correctly propagated for container types by using ContainerElementPredicate to traverse into their generic types. Refactored validation logic for clarity.

How Has This Been Tested?

Verified with FixtureMonkeyOptionsTest.strictModeNestedListValidExpression().

Is the Document updated?

N/A

@Chanwon-Seo
Copy link
Contributor Author

I've created a test case for this issue, which you can check out at the following link.
Also, I was wondering if there are any other counterexamples I might have missed regarding this problem.

@seongahjo
Copy link
Contributor

@Chanwon-Seo
This feature is more complex in the current architecture.
Could you implemenet this feature after this PR is merged? It will be more simple.

Would you mind if I closed the PR?

@seongahjo seongahjo removed this from the 1.1.16 milestone Feb 25, 2026
@seongahjo seongahjo closed this Feb 27, 2026
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.

"No matching results for given container expression" error in 1.1.15

2 participants