Autogeneration UTSettings.kt -> settings.properties (and probably some settings.md as well) #1396
Replies: 2 comments
-
I propose:
|
Beta Was this translation helpful? Give feedback.
-
As for settings, the only "conflict-prone" intersection we have in fuzzing, namely global useFuzzing=true/false may conflict with local fuzzingValue=0.0..1.0 Except this unique case set of local UI settings don't insersect with global set of "core" or "low-level" settings. Plugin-specific settings
Instead we just should provide self-documented global config file (if absent) with all existing defaults for possible manual tuning. |
Beta Was this translation helpful? Give feedback.
-
{USER_HOME}/.utbot/settings.properties is configuration for Intellij Plugin, CLI and CI and obviously it should be well documented.
At the moment main "source of knowledge" is documentation inside the code, namely UtSettings.kt
The idea is to generate a template for settings.properties as resource file to be distributed together with the plugin from the existing sourcecode.
'Template' here means that every key=value line inside the file should be commented and relative documentation should be provided above it. One can easily uncomment the line and adjust the value to get desired behavior.
Tomcat config file is well-known example of industry standard we may stick to.
Beta Was this translation helpful? Give feedback.
All reactions