-
-
Notifications
You must be signed in to change notification settings - Fork 22
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 compile warnings breaking builds with -Werror. #31
Conversation
Codecov Report
@@ Coverage Diff @@
## master #31 +/- ##
==========================================
+ Coverage 88.61% 88.66% +0.04%
==========================================
Files 37 37
Lines 3592 3590 -2
==========================================
Hits 3183 3183
+ Misses 409 407 -2
Continue to review full report at Codecov.
|
Hi @EmilyBjoerk and thanks for the work. Have you checked if a modification of the included json library is really necessary? The version we are using here is pretty old now and I saw a PR on that topic -> will this fix the issue as well? Then we can just update the library |
I think pulling a newer version from upstream might fix it, we can try that first. |
Co-Authored-By: Moritz Wirger <lj.moritorii@web.de>
Please let me know when you have updated the json library from upstream, their file structure seemed significantly different from what I saw in your repo. I'm not sure if they compile the source into one file or if your version is prior some refactoring so I'm not confident doing the update in this PR. |
If the user wishes to connect to a specific bridge it makes sense for them to remeber the bridge by and scan for the bridge by comparing MAC addresses as these are more stable than IPs in an ipv4 DHCP network. In order for the MAC address comparison to be stable, the user should use the same normalisation scheme as the library. Exposing this function to the user makes their life easier.
I switched to another JSON library nlohmann-json, which I wanted to do for some time now, the changes are on the development branch |
I'm unfamiliar with your git workflow, looking at the history I would have expected to see back merges from master to development but it seems you rebase/cherrypick instead? I'm not quite sure how you want me to do this. The changes I've made are basically trivial and I wonder if it isn't easier for you to just replicate them with your familiar workflows at this point? I've forked and fixed what I needed on my fork and now completed/deployed my project already so I'm not that concerned one way or another about the contribution "credit". |
@EmilyBjoerk No worries, changes are pushed and pullrequests are merged with the development branch first, then once the changes have been checked and they're stable they get merged into the master branch technically creating a new version of the library. Maybe it's time to create a contribution guide. Also nice project BTW 😄 |
@EmilyBjoerk I've tested your code with the changes made on the development branch and it all works fine. |
Ran into some problems pulling in hueplusplus into my project that uses strict flags for warnings.
Fixes some sign mismatches and implicit fall through and missing initializer.