fix: fixed no launch error during the build

[sigmaaa]

Description

Steps to reproduce:

• create a project
• build it
• during the build, create a new project
• try to build
• in most cases that cases "no launch" error during the build until close/reopen the project

Fixes # (IEP-1189)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)

How has this been tested?

• create a project
• build it
• during the build, create a new project
• try to build

Test Configuration:

• ESP-IDF Version:
• OS (Windows,Linux and macOS):

Dependent components impacted by this PR:

• Component 1
• Component 2

Checklist

• PR Self Reviewed
• Applied Code formatting
• Added Documentation
• Added Unit Test
• Verified on all platforms - Windows,Linux and macOS

Summary by CodeRabbit

• Bug Fixes
  • Ensured a configuration exists before creating a default debug configuration to prevent issues during the disposal of widgets in the project creation wizard.

[coderabbitai]

Walkthrough

This update introduces a preventive measure in the NewIDFProjectWizard.java file, ensuring that a configuration exists prior to the creation of a default debug configuration during widget disposal. The aim is to enhance stability and reliability in the project setup process.

Changes

File Path	Change Summary
.../idf/ui/wizard/NewIDFProjectWizard.java	Added check for existing configuration before creating default debug configuration during widget disposal.

Related issues

• Version 2.6.0 ESP-IDF Eclipse plugin still has indexer issues (IEP-752) #587: This issue discusses persistent GUI C++ errors due to indexing issues, which might be indirectly related to project setup and configuration handling improvements.
  • Reasoning: While the PR does not directly address GUI C++ errors, improvements in project configuration handling could influence overall plugin stability and error management.
• Indexer issue "symbol could not be resolved" related to using "#pragma once" in header files (IEP-755) #590: The problem of "symbol could not be resolved" might be rooted in how projects and their configurations are initialized and managed.
  • Reasoning: Enhancing project setup and configuration checks could potentially mitigate issues related to symbol resolution by ensuring a more stable environment for the indexer.

🐇🎉
In the garden of code, where the projects grow,
A rabbit hopped in, with a fix in tow.
"No more errors," it said with a grin,
"For I check configurations before I begin."
With each hop and a skip, it made things right,
Leaving a trail of green tests in the 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?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 1

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 4ede117 and 94ff75d.

Files selected for processing (1)

• bundles/com.espressif.idf.ui/src/com/espressif/idf/ui/wizard/NewIDFProjectWizard.java (1 hunks)

[alirana01]

LGTM!
Just a minor comment that is also given by coderabbit