We could simply use local storage until the modification is submitted.
Use case:
the user is working on editing the map
he does not push his modifications yet
when he comes back, a new version is available, the map is loaded from the local storage but he gets a message like "a new version is available" blablabla.
he can reset his modification and use the config file
he can keep on working on the map
he submits the modifications, his local storage becomes empty and he uses the config file again.
TL;DR: use local storage as soon as there is something in it, otherwise use config.js. The user can clear his local storage (to use config.js again).
That's basically what i've in mind, except the part where the local storage is cleared upon map submission. This is a nice adition ;) I'll try to implement everything tonight!
Here are my thoughts.
We could simply use local storage until the modification is submitted. Use case:
TL;DR: use local storage as soon as there is something in it, otherwise use config.js. The user can clear his local storage (to use config.js again).