diff --git a/CHANGELOG.md b/CHANGELOG.md
index 8f92b80fa..d9db3990f 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -17,6 +17,21 @@
All notable changes to the "Espressif IDF" extension will be documented in this file.
+## [1.0.1](https://github.com/espressif/vscode-esp-idf-extension/releases/tag/v1.0.1)
+
+### Features and enhancements
+
+- [Add remove CMakelists.txt elements](https://github.com/espressif/vscode-esp-idf-extension/pull/330)
+- [Add ESP32-S3 and ESP32-C3 idf targets](https://github.com/espressif/vscode-esp-idf-extension/pull/338)
+- [Add ESP-IDF validation for heap tracing and sdk configuration editor](https://github.com/espressif/vscode-esp-idf-extension/pull/347)
+- [New Project Wizard](https://github.com/espressif/vscode-esp-idf-extension/pull/171)
+
+### Bug Fixes
+
+- [Fix WSL 1 Flashing](https://github.com/espressif/vscode-esp-idf-extension/pull/331)
+- [Fix compiler in settings.json](https://github.com/espressif/vscode-esp-idf-extension/pull/334)
+- [Fix relative links in tasks output](https://github.com/espressif/vscode-esp-idf-extension/pull/337)
+
## [1.0.0](https://github.com/espressif/vscode-esp-idf-extension/releases/tag/v1.0.0)
### Features and enhancements
diff --git a/docs/COVERAGE.md b/docs/COVERAGE.md
index cbb491fe4..bf40c89d9 100644
--- a/docs/COVERAGE.md
+++ b/docs/COVERAGE.md
@@ -11,7 +11,7 @@ Make sure you had properly configure xtensa toolchain in `idf.customExtraPaths`
## Editor Coverage
-For the text editor highlighting, we use execute a child process with `gcovr -r . --gcov-executable xtensa-esp-elf-gcov --json`.
+For the text editor highlighting, we use execute a child process with `gcovr -r . --gcov-executable {TOOLCHAIN_PREFIX}-gcov --json`.
> **NOTE:** This assumes you had configure your extension with Xtensa toolchain in `idf.customExtraPaths` and installed the `gcovr` from Debug adapter's python requirements.
@@ -25,7 +25,7 @@ You can customize highlight color using the extension settings. Visual Studio co
## HTML report
-We execute a child process with command `gcovr -r . --gcov-executable xtensa-esp-elf-gcov --html` for the HTML report.
+We execute a child process with command `gcovr -r . --gcov-executable {TOOLCHAIN_PREFIX}-gcov --html` for the HTML report.
> **NOTE:** This assumes you had configure your extension with Xtensa toolchain in `idf.customExtraPaths` and installed the `gcovr` from Debug adapter's python requirements.
diff --git a/docs/FEATURES.md b/docs/FEATURES.md
index d4a914937..952f54252 100644
--- a/docs/FEATURES.md
+++ b/docs/FEATURES.md
@@ -45,7 +45,7 @@ Click F5 to start debugging. To configure the debug behaviour, please
On CMakeLists.txt file right click this extension provides a custom CMakeLists.txt Editor to fill an ESP-IDF Project and Component registration as specified in [ESP-IDF Project CMakeLists.txt](https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/build-system.html#project-cmakelists-file) and [ESP-IDF Component CMakeLists.txt files](https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/build-system.html#component-cmakelists-files). You need to choose which kind of CMakeLists.txt file (project or component) to edit. There is 2 types of input, one is a simple string and another is an array of strings, such as Component Sources (SRCS). All inputs are described in the CMakeLists.txt Schema (\${this_repository}/src/cmake/cmakeListsSchema.json).
-> **NOTE** This editor doesn't support all CMake functions and syntaxes. This editor should only be used for simple CMakeLists.txt options such as component registration (using idf_component_register) and basic project elements. If you need more customization or advanced CMakeLists.txt, consider reviewing [ESP-IDF Build System]((https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/build-system.html). Also review [CMakeLists.txt editor schema](../cmakeListsSchema.json) for a list of supported code.
+> **NOTE** This editor doesn't support all CMake functions and syntaxes. This editor should only be used for simple CMakeLists.txt options such as component registration (using idf_component_register) and basic project elements. If you need more customization or advanced CMakeLists.txt, consider reviewing [ESP-IDF Build System](https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/build-system.html). Also review [CMakeLists.txt editor schema](../cmakeListsSchema.json) for a list of supported code.
## Flash
diff --git a/schema.i18n.json b/schema.i18n.json
index b344cb4e9..6bd35af68 100644
--- a/schema.i18n.json
+++ b/schema.i18n.json
@@ -76,6 +76,7 @@
"espIdf.configDevice.title",
"espIdf.menuconfig.start.title",
"espIdf.cmakeListsEditor.start.title",
+ "espIdf.disposeConfserverProcess.title",
"espIdf.newProject.start.title",
"espIdf.setDefaultConfig.title",
"espIdf.selectPort.title",
diff --git a/src/cmake/cmakeListsBuilder.ts b/src/cmake/cmakeListsBuilder.ts
index 97693cff2..4587e03f3 100644
--- a/src/cmake/cmakeListsBuilder.ts
+++ b/src/cmake/cmakeListsBuilder.ts
@@ -59,16 +59,13 @@ export function parseCmakeListsText(
if (resultStr && resultStr.length > 1 && resultStr[1].length > 1) {
let newElement: CmakeListsElement = JSON.parse(JSON.stringify(element));
newElement.value = [];
- newElement.value =
- element.type === "array"
- ? resultStr[1].trim().replace(/\"/g, "").split(" ")
- : [resultStr[1].trim()];
switch (element.type) {
case "array":
- newElement.value = resultStr[1]
- .trim()
- .replace(/\"/g, "")
- .split(" ");
+ const listStr = resultStr[1].trim().replace(/\"/g, "");
+ if (listStr) {
+ newElement.value =
+ listStr && listStr === " " ? [listStr] : listStr.split(" ");
+ }
break;
case "binary_data":
if (resultStr[1]) {
diff --git a/src/views/cmakelists-editor/CmakeListsEditor.vue b/src/views/cmakelists-editor/CmakeListsEditor.vue
index eab6d9acb..045318ef8 100644
--- a/src/views/cmakelists-editor/CmakeListsEditor.vue
+++ b/src/views/cmakelists-editor/CmakeListsEditor.vue
@@ -54,7 +54,7 @@