Improved DotUtils for better type handling #9
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 refactors and enhances the utility methods for extracting nested properties from maps in the
DotUtilsclass, improving support for dot-notated paths and type safety. It also updates related tests to verify the new behaviors and fixes import usages for test fixtures. The most significant changes are grouped below:DotUtils enhancements
mapFrom,listFrom, andarrayFrommethods inDotUtilsto support extraction from nested properties using dot-notated paths and improved type safety checks. Added a new typed variantlistFrom(Map<String, Object> source, String property, Class<T> clazz)for extracting lists of a specific type. [1] [2]getObjectFromSource(for traversing nested map paths) andconvertToObjectArray(for safely converting primitive arrays toObject[]).PathCommon improvement
PathCommon#getPropertyValueto fall back to map access when the source object is aMapand the property exists, increasing robustness for mixed data types.