Use saner names for the pin attributes #4
Merged
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.
I think that
d_or_c
is as confusing asdc
, possibly more, when the parameter is still calleddc
. If we wanted to be hyper-correct and stick to Python's style, we should call itdata_or_command
, but then for consistency we would also need things likemaster_in_slave_out
and so on, and I think this is an overkill. Since the pin is usually labelleddc
on the physical modules anyways, I think it's perfectly fine to use that — it's also consistent with the usage in Arduino and other drivers. I added_pin
to make the linter be quiet and also to clarify that this is indeed a pin. I also changed the name ofres
toreset_pin
to be consistent (the label for that pin on the modules is sometimesrs
and sometimesrst
so keeping the shortcut is not helpful).