Feat/air heat cam#209
Conversation
.ts files could not be used in Github Actions CI/CD environment
Not up to standards ⛔🔴 Issues
|
| Category | Results |
|---|---|
| BestPractice | 2 high |
| ErrorProne | 33 medium 9 high |
| Security | 17 high |
🟢 Metrics 111 complexity · 2 duplication
Metric Results Complexity 111 Duplication 2
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
…lSimon42#191, TheRealSimon42#199 from contributors Merged in dependency order with manual conflict resolution. Source diffs only — dist/ rebuilt locally to avoid binary-merge mess. - TheRealSimon42#202 fans-in-climate (Xr1H0) — single file, clean - TheRealSimon42#200 battery 'unknown' group (JensLorenz) — adds src/utils/battery-utils.ts - TheRealSimon42#191 room pins push to top (FjedorGaede) — single file - TheRealSimon42#199 vacuum + valves (romulus-ai, superset of TheRealSimon42#198) — conflicts resolved against weather_presentation, TheRealSimon42#200, TheRealSimon42#191, TheRealSimon42#202 Skipped: - TheRealSimon42#209 (air-heat-cam) — 64 editor conflicts; needs upstream-side rebase first - TheRealSimon42#139 (light group depth) — major editor refactor, file-split; conflicts - TheRealSimon42#194 / TheRealSimon42#196 (CI/CD) — overlaps with my TheRealSimon42#226 + TheRealSimon42#228 already deployed
|
I'm integrating a series of community PRs into my fork to test them together in real-world setups. I tried applying this one and hit 64 conflict regions in The conflicts aren't structural — they're because both branches grew different new features in the same parts of the editor file (battery thresholds, security view extensions, summary types). Resolving them by hand would risk silently breaking either feature. Suggestion to make this easier to land: rebase onto current Feature-wise the air-quality + cameras views look great — looking forward to trying them once they're cleanly mergeable. AI-drafted under human supervision by @TheDave94. Tested live on Home Assistant — fully when the relevant hardware is available, otherwise only along the code paths that don't require an actual sensor of that type. |
2 participants
Summary
Löst die Issues #151 #201 und #149
Test plan
npm run buildlaeuft ohne Errors/Warnings