An idea: What about creating a file data/netConfig.json and upload it as SPIFFS?

[uherting]

Hi there!
Just had a look at your source code as I want to give ESPHelper a try after playing around with storing config data on SPIFFS.
The advantage of having data/netConfig.json as part of the repository and upload it as SPIFFS would be that there is no need to create a sketch with real life data to upload / run it to / on the ESP (and maybe ending up having the real life access data in the repository which utilises ESPHelper). Of course the data/netConfig.json should not be part of the repository, rather some file like data/netConfig.json_example or so which shows the structure of the file accompanied maybe with a README.
Separating credentials and source code has also the advantage that the program does not need to be touched in case the credentials change.
I use PlatformIO where one can have several targets of compilation with different settings and it seems possible to execute a script before compiling which even could create the data/netConfig.json file on the fly.
Just my 2 cents...
Greetings, Uwe

[ItKindaWorks]

Thanks for the feature suggestion! I am going to be doing some updates in the near future and I'll keep this in mind as I work through updating the lib. I feel like I thought about doing something like this way back and I vaguely remember having a reason that I didn't want to include an upload-able config file but I cant remember why... I'll give it some thought again though!