-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Fix #ifdefs #8853
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix #ifdefs #8853
Conversation
Hey there @OttoWinter, mind taking a look at this pull request as it has been labeled with an integration ( |
To use the changes from this PR as an external component, add the following to your ESPHome configuration YAML file: external_components:
- source: github://pr#8853
components: [debug]
refresh: 1h (Added by the PR bot) |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## dev #8853 +/- ##
==========================================
+ Coverage 53.70% 56.66% +2.95%
==========================================
Files 50 50
Lines 9408 9938 +530
Branches 1654 1341 -313
==========================================
+ Hits 5053 5631 +578
+ Misses 4056 3960 -96
- Partials 299 347 +48 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
The PR corrects the nesting of #ifdef
guards so that on_shutdown()
is only compiled when USE_ESP32
is defined, fixing a compilation error.
- Moved the
on_shutdown()
declaration outside theUSE_SENSOR
guard - Added a dedicated
USE_ESP32
block aroundon_shutdown()
- Ensured matching
#endif
comments
What does this implement/fix?
Fix compilation error due to incorrect nesting of #ifdefs.
Types of changes
Related issue or feature (if applicable):
BETA
[debug] error: no declaration matches 'void esphome::debug::DebugComponent::on_shutdown()' issues#7030Pull request in esphome-docs with documentation (if applicable):
Test Environment
Example entry for
config.yaml
:# Example config.yaml
Checklist:
tests/
folder).If user exposed functionality or configuration variables are added/changed: