chore: include shader paths for IDE code completion

[sicsix]

• Adds feature shaders and the root shaders folder to the project includes to allow for code completion

Summary by CodeRabbit

• Chores
  • Updated build configuration to automatically include shader directories from feature subfolders and explicitly include the package shader directory. No changes to application behavior.

[coderabbitai]

Walkthrough

The CMake configuration was updated to automatically detect and include all "Shaders" directories within feature subfolders as private include directories. Additionally, the configuration now explicitly includes the "package/Shaders" directory. No changes were made to build logic, linking, or public interfaces.

Changes

File(s)	Change Summary
CMakeLists.txt	Added globbing for "features/*/Shaders" directories and included them as private include directories; explicitly added "package/Shaders" to include paths.

Poem

In the warren of features, shaders now found,
Each hidden burrow, their paths now abound.
CMake’s keen nose sniffs folders anew,
Gathering shaders, as rabbits would do.
With every build hop, the search is complete—
All shaders included, the project’s now neat!
🐇✨

---

🪧 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.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (2)

CMakeLists.txt (2)

60-66: Sort and consolidate shader include directories
The FEATURE_SHADER_DIRS list may be processed in arbitrary filesystem order, leading to non-deterministic include statements in your IDE project. Sort the list for stable ordering, and you could merge multiple target_include_directories calls into one block to simplify maintenance:

+list(SORT FEATURE_SHADER_DIRS)
 foreach(_dir IN LISTS FEATURE_SHADER_DIRS)
     target_include_directories(
         ${PROJECT_NAME}
         PRIVATE
           "${CMAKE_SOURCE_DIR}/${_dir}"
     )
 endforeach()

---

73-74: Guard manual include of package/Shaders against missing folders
If package/Shaders is ever moved or deleted, CMake will error out. Wrap the explicit include in an existence check:

-       "${CMAKE_SOURCE_DIR}/package/Shaders"
+if(EXISTS "${CMAKE_SOURCE_DIR}/package/Shaders")
+  target_include_directories(${PROJECT_NAME} PRIVATE "${CMAKE_SOURCE_DIR}/package/Shaders")
+endif()

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 0b7f208 and 8d7e750.

📒 Files selected for processing (1)

• CMakeLists.txt (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: build plugin and addons

[github-actions]

✅ A pre-release build is available for this PR:
Download