Closed tekktrik closed 2 years ago
can you check if any examples/code use the old naming?
Will do!
It looks like all the pin arguments in the examples in the repo are named esp32_*
like esp32_reset
. Should I check the Learn guides as well, or would those reference/be linked to the examples?
yah check the learn system, its kinda risky to change arg names :/ lots of code can break
A quick search for ESP32 products and reading the guides shows that the examples (no references other than code examples) always use the same variable naming scheme of esp32_*
and the arguments are never done as keywords, only positional.
Is this all good? Happy to do anything needed if this is a viable PR still!
@jerryneedell any thoughts? just cause you deal with this stuff more recently than i!
No concerns from me. Thank you for asking!
That said, I suppose it should be considered a "breaking" change and announced in the release.
Any decision on this? Happy to change the names to something else as well if those aren't clear.
Sounds good! I'd be happy to look into how easily they can get a PR without breaking code!
Addresses Issue #121 by changing relevant argument names from
*_pin
to*_dio
. I chose this instead of just using*
argument names so it would be explicitly clear it should be aDigitalInOut
instance passed as the argument, and also because I know there is areset
parameter so that argument wouldn't be confused for a boolean argument or something like that.