The reason is that for a lot of work, local is simply faster with file save changes.
The remote is to see things as they would be in production, and for some features (like functionality based on different domain names) it is impossible on local.
Like I said, I can adjust. If you remove the option to have multiple development targets, I can setup a hosts file pointing to localhost and go that route to work on the multi-tenant custom domain work I have. There is also ngrok, etc. if that need arises. I don’t think restricting to 1 dev target is a good change, but I can deal with it.
But here’s the thing you guys often miss. I’M REPORTING A BUG. I reported this particular bug, because YOU ALLOW two development targets. And since you allow two development targets, it should work.
Please don't do that.
We often work on three targets - local dev, remote dev, and remote production.
Local dev, as Ken pointed out, is great for quick file save not having to wait ages for Wappler FTP to upload the file.
Remote dev is good for quickly fixing a bug found on remote server environment (after local is deployed there).
I am sure there will still be problems with synching and DB even if you put hard limit, because the reason is lack of user knowledge and docs - and not because Wappler has a feature to support multiple targets.