Chore/sql format refactor block class #290
Merged
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 PR performs a structural refactoring of the formatter code in preparation for merging into the main development branch. The purpose is to improve maintainability and prepare for future syntax support.
Changes Included:
Modularization of block classes
The formatter’s internal block classes have been split to support more granular syntax rules (e.g., upcoming features for new SQL constructs).
Introduction of SqlBlockFormattingContext
Constructor parameters for block classes are now consolidated into a single context class (SqlBlockFormattingContext) for better readability and manageability.
Child block properties based on query structure
Properties representing child blocks have been added to each block class to better reflect the structural relationship within SQL queries.
(Note: actual usage of these properties will be implemented in a separate PR.)
Package reorganization
Relevant classes have been moved to new packages to improve modular separation.
Notes:
This PR includes some unused classes and methods that will be utilized in future formatter functionality.
No functional changes to formatting output are introduced at this stage.
This is a preparatory step for cleaner, extensible formatter development.