Added DotUtils and parsePaths to help build path components list #7
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 utility methods for extracting map, list, and array properties from objects, introduces a new path parsing utility, and improves modularity and test coverage. The most important changes are grouped below.
Utility Extraction and Refactoring
mapFrom,listFrom, andarrayFrommethods fromDotPathQLto a new utility classDotUtils, improving separation of concerns and making these utilities statically accessible. All usages throughout the codebase and documentation were updated to referenceDotUtilsinstead ofDotPathQL. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19]Path Parsing Feature
DotUtils.parsePathsmethod and supporting parser classes (PathParser,DotParseinterface, and factory method inDotPathFactory) to robustly parse dot-notated path strings, including nested bracket expressions. This enables more advanced path parsing scenarios. [1] [2] [3] [4] [5] [6]Documentation Updates
README.mdto reflect the new usage ofDotUtilsfor utility methods and introduced a new section describing the map object conversion and path parsing capabilities. [1] [2]Test Improvements
UtilsTest.javatoDotUtilsTest.javaand added comprehensive tests for the new path parsing functionality, including edge cases and invalid input handling. Updated existing tests to useDotUtilsinstead ofDotPathQL. [1] [2] [3] [4] [5] [6] [7]Minor Cleanups
@SuppressWarnings("unchecked")fromDotPathQL, and cleaned up unused helper methods. [1] [2]These changes make the codebase more modular, easier to maintain, and extend the functionality for path parsing and object property extraction.