[amahlaka]

I have been wondering why doesn't pilight handle configuration editing and problems properly
Instead of removing the config file contents, wouldn't it be better to notify user or maybe move the invalid config to config.json.old or something similar

Also, why won't pilight keep edits that are made while it's running after a restart, does it store running config in memory and write it to file again and again?

[pilino1234]

Instead of removing the config file contents

When does this happen??

Also, why won't pilight keep edits that are made while it's running after a restart, does it store running config in memory and write it to file again and again?

The pilight daemon keeps the current config in memory after restart, where it is updated with new values over time. When the daemon is stopped, the changes are written back to disk - there is only one write. This will obviously override all changes made to the file in the meantime.

[amahlaka]

When does this happen??

When there is typo on config and I start pilight the file gets erased

[wo_rasp]

Also, why won't pilight keep edits that are made while it's running after a restart, does it store running config in memory and write it to file again and again?

If you do this it does damage the SD card after a while, as you exceed the number of write cycles.
I know that there are methods available to circumpass this bottleneck, but that is the way it is currently implemented.

[pilino1234]

When does this happen??

When there is typo on config and I start pilight the file gets erased

Which pilight version are you using? This shouldn't happen, pilight should just show the offending error in the config in the debug output and exit. The file should never be erased.