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
Sonoff: improve device compliance #627
Sonoff: improve device compliance #627
Conversation
72417ec
to
b283721
Compare
a3d3af7
to
e9b14a3
Compare
a5e13e7
to
e0c63bf
Compare
Please @Pierre-Gilles don't forgot this PR, it a great refactor :) |
@atrovato Don't worry, but the PR is really huge so it'll take a lot of time to review it. For now all my time is dedicated to the scene feature, hope you'll understand! 😄 |
I understand, please don't forget it :) |
08476e3
to
7270ffd
Compare
Hi ! I'm reviewing your PR and wanted to see the code coverage, I don't understand why the coverage is never reported on this PR specifically (works with other PR...) I think it's because tests are passing on your CircleCI, not Gladys Assistant CircleCI ! Any idea ? |
It don't work all the time, on other PR too. |
a8ddf8c
to
a040e91
Compare
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.
Hi !
First, thanks for this really great PR ! 🙂
There is lots of work here, and quality work, no doubt =)
I noted a few feedbacks, most of them are just question, no change required.
There is just 2-3 comments with minor changes asked, but otherwise the rest of the code is perfect !
I'm looking forward to your answers to integrate this into Gladys !
front/src/components/boxs/device-in-room/device-features/BinaryDeviceFeature.jsx
Outdated
Show resolved
Hide resolved
I have following URL on push coverage step: But ****** should be GladysAssistant or atrovato. |
When I think about it I'm not sure this can work... Does codecov allow a forked repo to push data on my Codecov account ? I think it would be a security issue and I don't know if they allow that No worries, I can push your branch on Gladys main repo before merging to have a full build in any case. |
In fact, it works on other PR from fork! Example: https://codecov.io/gh/GladysAssistant/Gladys/pull/675 Maybe you are doing something differently? Did it work in the past for others PR you did? |
Ok, for test coverage, I unfollow my own GitHub repository, URL looks good for now. |
Codecov Report
@@ Coverage Diff @@
## master #627 +/- ##
==========================================
+ Coverage 91.88% 92.05% +0.16%
==========================================
Files 393 410 +17
Lines 4967 5134 +167
==========================================
+ Hits 4564 4726 +162
- Misses 403 408 +5
Continue to review full report at Codecov.
|
e5fd100
to
32ff778
Compare
…#627) * Sonoff: improve pow device and mqtt topics * Sonoff: manage Dual R2 * Sonoff: dual R2 setValue Power1/2 * Sonoff: add arilux-lc01 device * Sonoff: split methods * Sonoff: improve test coverage * Sonoff: refactor device list * Sonoff: manage Sonoff SV device * Sonoff: manage Sonoff Dual device * Sonoff: manage 4CH device * Sonoff: rename device files * Sonoff: manage Slampher device * Sonoff: manage Sonoff Touch device * Sonoff: manage Sonoff LED device * Sonoff: manage 1/4 Channel devices * Sonoff: fix device discover * Sonoff: edit device features * Sonoff: delete manual creation * Sonoff: refactor device box * Sonoff: fix typo * Sonoff: refactor device and handle updates * Sonoff: fix refactor impacts * Sonoff: manage not managed device * Sonoff: oops - fix tests * Sonoff to Tasmota * Tasmota: add more devices * Tasmota: refactor feature discovering * Tasmota: dynamic discover * Tasmota: add components * Tasmota: improve UI * Tasmota: fix feature label and icon * Tasmota: display featuren name * Tasmota: remove front pagination * Tasmota: rollback dashboard display
Pull Request check-list
To ensure your Pull Request can be accepted as fast as possible, make sure to review and check all of these items:
npm test
on both front/server)npm run eslint
on both front/server)npm run prettier
on both front/server)- [ ] If your changes modify the API (REST or Node.js), did you modify the API documentation? (Documentation is based on comments in code)- [ ] If you are adding a new features/services which needs explanation, did you modify the user documentation? See the GitHub repo and the website.front/src/config/demo.json
) so that the demo website is working without a backend? (if needed) See https://demo.gladysassistant.com.NOTE: these things are not required to open a PR and can be done afterwards / while the PR is open.
Description of change
Complete the device compatibility.
Remove manual creation.
Rename to Tasmota.