Skip to content
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

Allow showing static IP config without predefined value #365

Merged
merged 3 commits into from
Sep 8, 2017

Conversation

vyruz1986
Copy link
Contributor

Previously a valid predefined static IP had to be passed before the
config page would show the IP, gateway and subnet fields. This did not
allow the config page to show 'optional' static IP fields.
Now a boolean can be passed to the autoConnect() function which will
specify whether the static IP fields should be shown or not.
When this boolean is true but no predefined values are passed and fields
are left blank in config page, wifiManager will revert to DHCP. This
allows user to choose between static IP or DHCP without changing code

For backwards compatibility we will show the static IP fields regardless of how the boolean is set.

vyruz1986 added 3 commits May 4, 2017 21:59
Previously a valid predefined static IP had to be passed before the
config page would show the IP, gateway and subnet fields. This did not
allow the config page to show 'optional' static IP fields.
Now a boolean can be passed to the autoConnect() function which will
specify whether the static IP fields should be shown or not.
When this boolean is true but no predefined values are passed and fields
are left blank in config page, wifiManager will revert to DHCP. This
allows user to choose between static IP or DHCP without changing code
Regardless of the boolean, we should always show static IP fields if
actual static IP value is passed. This ensures backwards compatibility
@tablatronix tablatronix added the enhancement Feature Request label Aug 30, 2017
@tablatronix tablatronix added this to the dev milestone Aug 30, 2017
@tablatronix
Copy link
Collaborator

I think the argument should be dropped, and replaced with a setter for this option. We probably do not want to clog up the argument list with flags or options.

@vyruz1986
Copy link
Contributor Author

That makes sense to me, are you going to implement this or do you want me to do it?

@tablatronix
Copy link
Collaborator

I can tweak it after pulling it in

@tablatronix
Copy link
Collaborator

hmm ill have to cherry pick it into development

@tablatronix tablatronix changed the base branch from master to development September 8, 2017 21:18
@tablatronix
Copy link
Collaborator

tablatronix commented Sep 8, 2017

oh nm you can change pr base now do it from the web !

@tablatronix tablatronix merged commit f59c150 into tzapu:development Sep 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Feature Request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants