fix: exclude API to handle primitive collection or arrays #3
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.
This pull request enhances the handling of primitive arrays in the
PathExcludeclass and refactors test fixtures to use static factory methods for object creation, improving code clarity and maintainability. It also adds new fields to support primitive arrays in test data and updates related logic accordingly.Core logic improvements
PathExclude: AddedisPrimitiveArraycheck to return primitive arrays directly, preventing casting errors and ensuring correct processing. [1] [2]addElementsToList, improving readability and separation of concerns. [1] [2]Test fixture enhancements
of123,ofOrder123) to test classes and records (Address,Occupation,Order,Product) for more concise and reusable test object creation. [1] [2] [3] [4] [5] [6] [7] [8]UserDetailclasses and records to use new factory methods and added a newscoresArrayfield to support primitive array testing. [1] [2]Minor changes