Skip to content

Conversation

@TimoPtr
Copy link

@TimoPtr TimoPtr commented Sep 28, 2025

I made a mistake while configuring this component with the pin. The mistake was obvious and could have been avoid if the pin selection was using the ESPHome pin representation that checks the pin for the selected board. This PR does replace the int representation of a pin with a stronger type from ESPHome.

I added a .gitinore file and VSCode did fix some formatting issues.

@RobertJansen1
Copy link
Collaborator

we try to keep the changes to the core files to a minimum (pin config as an exception) is it possible to rewrite the change to not change the core files?

next to that, can you remove the .gitignore from the pull request?

@TimoPtr
Copy link
Author

TimoPtr commented Oct 2, 2025

we try to keep the changes to the core files to a minimum (pin config as an exception) is it possible to rewrite the change to not change the core files?

Unfortunately I don't know if we can mix the two solution for setting up the pin and also it is not using the same function to interact with the pins.
A solution could be using InternalGPIOPin to try to get the pin as a uint8 to give it then to core, but again I'm not super familiar with the API.

About the changelog do you prefer a second PR? or no .gitignore at all?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants