Skip to content

Conversation

@kolipakakondal
Copy link
Collaborator

@kolipakakondal kolipakakondal commented Jun 9, 2025

Description

Adding preview targets in the IDE
https://esp32.com/viewtopic.php?t=45765

Fixes # (IEP-1551)

Type of change

  • This change requires a documentation update

How has this been tested?

NA

Test Configuration:

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

Dependent components impacted by this PR:

  • Configuring the preview targets such as esp32c5

Checklist

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

Summary by CodeRabbit

  • Documentation
    • Added a new step-by-step guide for configuring preview or custom ESP-IDF targets in the IDE, including toolchain and launch target setup instructions with examples and images.
    • Updated the "References" section to include a link to the new guide and improved formatting.

@coderabbitai
Copy link

coderabbitai bot commented Jun 9, 2025

Walkthrough

A new documentation file was added, providing step-by-step instructions for configuring custom or preview ESP-IDF targets in the IDE. Additionally, the build project documentation was updated to include a reference to this new guide and to correct the formatting of an existing reference entry.

Changes

File(s) Change Summary
docs/en/additionalfeatures/configuretoolchain.rst Added a new guide detailing manual configuration of custom ESP-IDF targets in the IDE.
docs/en/buildproject.rst Updated references section: fixed formatting and added a link to the new configuration guide.

Suggested labels

needs translation:CN

Suggested reviewers

  • sigmaaa
  • alirana01

Poem

In the warren of docs, a new path appears,
Custom targets now clear, allaying your fears.
With steps and with screenshots, the journey’s well lit,
Build and configure—your project will fit!
🐇✨


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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>, please review it.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • 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/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@kolipakakondal kolipakakondal requested a review from sigmaaa June 9, 2025 06:36
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (4)
docs/en/additionalfeatures/configuretoolchain.rst (2)

1-3: Verify title underline length

Ensure the sequence of = on line 2 matches or exceeds the length of the title on line 1, or the RST parser may misinterpret the section.


19-20: Leverage figure for captions

Using .. figure:: with :caption: yields built-in caption support and better semantics than an italicized paragraph following .. image::.

docs/en/buildproject.rst (2)

43-44: Maintain alphabetical order in References

For consistency, consider placing “Add a Preview or Custom ESP-IDF Target” before “Configure CDT Build Environment Variables” in the toctree.


45-45: Remove trailing whitespace

Line 45 contains only indentation; deleting it will clean up formatting and avoid formatting linter warnings.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 70a0ae5 and d2f034d.

⛔ Files ignored due to path filters (4)
  • media/toolchain/toolchain_1.png is excluded by !**/*.png
  • media/toolchain/toolchain_2.png is excluded by !**/*.png
  • media/toolchain/toolchain_3.png is excluded by !**/*.png
  • media/toolchain/toolchain_4.png is excluded by !**/*.png
📒 Files selected for processing (2)
  • docs/en/additionalfeatures/configuretoolchain.rst (1 hunks)
  • docs/en/buildproject.rst (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: build
  • GitHub Check: Build Espressif-IDE Docs
  • GitHub Check: build_macos

Comment on lines +16 to +18
.. image:: ../../../media/toolchain/toolchain_1.png
:alt: Core Build Toolchains Preferences (Add Custom Target)

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Invalid image paths will break docs build

The relative paths for your screenshots are off by one directory; from docs/en/additionalfeatures, you should use ../../media/... instead of ../../../media/....

--- a/docs/en/additionalfeatures/configuretoolchain.rst
+++ b/docs/en/additionalfeatures/configuretoolchain.rst
@@ -16,3 +16,3 @@
-.. image:: ../../../media/toolchain/toolchain_1.png
-  :alt: Core Build Toolchains Preferences (Add Custom Target)
+.. image:: ../../media/toolchain/toolchain_1.png
+   :alt: Core Build Toolchains Preferences (Add Custom Target)
@@ -29,3 +29,3 @@
-.. image:: ../../../media/toolchain/toolchain_2.png
-  :alt: CMake Toolchain Preferences (Add Custom Target)
+.. image:: ../../media/toolchain/toolchain_2.png
+   :alt: CMake Toolchain Preferences (Add Custom Target)
@@ -43,3 +43,3 @@
-.. image:: ../../../media/toolchain/toolchain_3.png
-  :alt: New ESP Target Dialog (Custom Target Example)
+.. image:: ../../media/toolchain/toolchain_3.png
+   :alt: New ESP Target Dialog (Custom Target Example)
@@ -54,3 +54,3 @@
-.. image:: ../../../media/toolchain/toolchain_4.png
-  :alt: Build Output for Custom Target Project
+.. image:: ../../media/toolchain/toolchain_4.png
+   :alt: Build Output for Custom Target Project

Also applies to: 29-31, 43-44, 54-55

🤖 Prompt for AI Agents
In docs/en/additionalfeatures/configuretoolchain.rst around lines 16 to 18, the
relative image paths are incorrect and cause the docs build to break. Change the
image paths from '../../../media/...' to '../../media/...' to correctly
reference the media directory relative to the current file. Also update the same
path correction for lines 29-31, 43-44, and 54-55.

@kolipakakondal kolipakakondal added this to the v3.5.0 milestone Jun 10, 2025
@kolipakakondal kolipakakondal merged commit 37521c1 into master Jun 10, 2025
5 of 6 checks passed
@kolipakakondal kolipakakondal deleted the IEP-1551 branch June 10, 2025 08:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants