Refact: better type field info #76
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 refactors how field types are represented and handled throughout the analyzer and code generator logic, moving from plain strings to the new
common.FieldTypestruct. This change improves type safety and makes it easier to handle composed types (such as slices). The updates touch both production and test code, ensuring consistent usage ofFieldTypeeverywhere field types are referenced or validated.Core refactoring:
common.FieldTypestruct in all relevant code paths, including struct definitions, validation logic, and test cases. [1] [2] [3] [4] [5]Analyzer logic updates:
FieldTypemethods and properties, improving correctness when handling nested and composed types. [1] [2]Test code modernization:
common.FieldTypestruct, ensuring tests validate the updated logic and type handling. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22]Imports and dependencies:
commonpackage to all affected files. [1] [2] [3] [4]Composed type support:
ComposedTypeproperty ofFieldType. [1] [2]