Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
@AdrianSoundy wouldn't be better to throw a bad argument exception instead of "fixing" the value?
I mean, as it is it works, of course, but the developer is not aware that he has made a mistake or set it to a wrong value.
That's the usual procedure throughout the code base and it's done in a number of places.
From what I could found (I've only worked with 8 and 16 bits) but the data can be from 8 to 16. I don't know if ESP32 can handle anything in the between...
So I suggest that the check is made for a valid number >= 8 and <= 16 (or just 8 and 16 to keep it simple) and throw an exception on invalid argument. What do you think?