feat: Add support for double default values #177
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.
🐛 Problem
When using the "set default values" option,
double
fields were not getting default values assigned, causing inconsistent behavior compared to other primitive types (int
,bool
,String
,List
).This could lead to:
✅ Solution
Added complete support for
double
default values across the entire codebase:Changes Made:
Settings.kt:
doubleDefaultValue: String = "0.0"
fielddoubleFieldDefaultValue(): String?
methodClassDefinition.kt:
double
case in field generation logicbool
andint
checks incorrectly usedstringFieldDefaultValue()
JsonInputDialog.kt:
int
andbool
fields🧪 Testing
📸 Before vs After
Before:
double
fields had no default valuesAfter:
double
fields get configurable default values (default: "0.0")🔗 Related Issues
Fixes the missing double default value support identified during codebase analysis.