Fix: Update platformio_override.sample.ini

[huckley]

Add custom_usermods to 433MHz RF example

Summary by CodeRabbit

• New Features
  • Introduced an updated configuration for RF433 environments that enables enhanced custom module support. Users with RF433-enabled setups will benefit from improved performance and feature support while existing functionality remains intact. The update delivers enhanced reliability and a smoother operation experience without interfering with established settings.

[coderabbitai]

Walkthrough

The change involves modifications to the [env:esp32dev_usermod_RF433] section of the platformio_override.sample.ini file. The line defining the build flags has been updated to remove the -D USERMOD_RF433 definition. Additionally, a new line has been introduced to specify a custom user module, custom_usermods = usermod_v2_RF433, indicating a change in the configuration for the RF433 user module.

Changes

File	Change Summary
platformio_override.sample.ini	Modified build_flags to remove -D USERMOD_RF433 and added custom_usermods = usermod_v2_RF433 in the [env:esp32dev_usermod_RF433] section.

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 3845bbf and f41379c.

📒 Files selected for processing (1)

• platformio_override.sample.ini (1 hunks)

🔇 Additional comments (2)

platformio_override.sample.ini (2)

536-536: Removal of Legacy Build Flag
The change on line 536 removes the -D USERMOD_RF433 flag from the build flags. This update aligns with the PR objective to deprecate the old definition. Please verify that no other parts of the configuration or dependent documentation still reference this flag.

---

537-537: Addition of Custom Usermods Configuration
The new line on 537 introduces custom_usermods = usermod_v2_RF433, which enables the updated RF433 user module feature. Ensure that the corresponding module (usermod_v2_RF433) is fully implemented and appropriately documented.

---

🪧 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.
  • Generate unit testing code 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 testing code 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 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 generate unit testing code.
  • @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.

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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.

[DedeHai]

thanks for the updated example. can ou remove the old definition while you are at it?

[Arcitec]

The entire lib_deps statement should be deleted too. That's handled automatically by the PlatformIO Libraries feature we use now.

In this case it's handled here now:

https://github.com/wled/WLED/blob/main/usermods/usermod_v2_RF433/library.json

So users only need to set custom_usermods, nothing else. :)

[Arcitec]

This is actually redundant now and would work equally well if deleted. If deleted, it automatically inherits those exact build flags from the extends.

The ${env:esp32dev.build_flags} is however vitally important if the user wants to add extra WLED build flags that configure the usermod, so the example should still stay.

But maybe change it to this:

;; Uncomment and append your own build flags here if you want to configure the usermod:
; build_flags = ${env:esp32dev.build_flags}