Closed alirana01 closed 7 months ago
The changes across various files in the Espressif IDF Eclipse plugin enhance the management of the configuration server. They introduce a more granular file-based control for the JSON configuration server, including a new key type for server mapping and additional parameters for server operations. This suggests a shift towards a more file-centric approach for managing configurations.
File Path | Change Summary |
---|---|
bundles/com.espressif.idf.sdk.config.core/src/com/espressif/idf/sdk/config/core/IDFConstants.java |
Added a comment to the declaration of ESP_CORE_DUMP_SCRIPT in the IDFConstants interface. |
bundles/com.espressif.idf.sdk.config.core/src/com/espressif/idf/sdk/config/core/SDKConfigPropertyTester.java |
Added import statement for StringUtil , refactored logic in test method. |
bundles/com.espressif.idf.sdk.config.core/src/com/espressif/idf/sdk/config/core/server/ConfigServerManager.java |
Replaced map key type, modified methods to accept both IProject and IFile , introduced ProjectFileMapKey class. |
bundles/com.espressif.idf.sdk.config.core/src/com/espressif/idf/sdk/config/core/server/JsonConfigServer.java |
Added imports, declarations, modified constructor, methods for handling file-based configuration. |
bundles/com.espressif.idf.sdk.config.ui/src/com/espressif/idf/sdk/config/ui/ConfigContentProvider.java |
Updated ConfigContentProvider to accept IFile parameter in constructor. |
bundles/com.espressif.idf.sdk.config.ui/src/com/espressif/idf/sdk/config/ui/LoadSdkConfigHandler.java |
Refactored code to handle resource selection, updated method calls. |
bundles/com.espressif.idf.sdk.config.ui/src/com/espressif/idf/sdk/config/ui/SDKConfigurationEditor.java |
Added import, modified methods to include file handling. |
"In code's woven warren, changes hop and bound,
🌟 With files and functions, new paths are found.
A rabbit's touch, so deft, so slight,
Config servers dance in the moonlit night."
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
@AndriiFilippov Can you verify this? Create a seperate configuration file for each target, maintain different settings, and then try to open them and save. See if you are able to save them to the same file that you have opened.
@alirana01 hi !
Steps: Create project - build project - change some settings in sdkconfg file - build project - delete sdk file - change some settings in sdk old file - build project - sdk.old.old created instead of sdkconfig. So it use sdk.old during build process instead of using sdkconfig file.
Once Build folder is deleted - build project - sdkconfig file created as it should be.
@alirana01 hi!
Steps:
Create project - build - open sdk and change some settings - build again - open sdk file - close sdk file - open sdk.old file - close sdk.old file - build project - it re-build entire project again.
- close sdk.old file - build project - it re-build entire project again.
Does it mean that sdk.old overwritting some of the settings in the original sdk file as well?
Description
By default the sdkconfig editor was only opening the sdkconfing file and even when manually opening other files with editor it was only showing contents of the default sdkconfig.
I have added required changes to configuration server to launch and handle different files at the same time on same project.
Fixes # (IEP-1103)
Type of change
Please delete options that are not relevant.
How has this been tested?
sdkconfig
in editor, change some settings, and build the project.sdkconfig.old
, make changes, and verify that changes do not affect other files.sdkconfig
is opened in thesdkconfig
editor when double-clicked.Test Configuration:
Checklist
Summary by CodeRabbit
New Features
Bug Fixes
Refactor
Documentation
Style