To make it easier to test and debug each part of the code, we can break up the main.cpp file into separate modules; the setup
and loop sections in main.cpp would call the functions from the other modules
For instance, we could divide main.cpp into the following modules:
- WiFi_management .cpp/.h (all the WiFi and web portal related code, not sure if the FS management should be a separate module in and of itself)
- button_presses .cpp/h
- Slack_status .cpp/h (query/send status&presence&DnD, most recent remote status)
- NTP_status .cpp/h (query NTP server, most recent time)
- local_status .cpp/h (LED state, most recent current status)
- deep_sleep .cpp/h (functions to sleep/wake board at night)
Perhaps we don't need 2 files for each module, but I saw there are some precedents on what things should go where.
To make it easier to test and debug each part of the code, we can break up the main.cpp file into separate modules; the setup
and loop sections in main.cpp would call the functions from the other modules
For instance, we could divide main.cpp into the following modules:
Perhaps we don't need 2 files for each module, but I saw there are some precedents on what things should go where.