I'd like to request you add validation against the remove function across RouterOS.
So that, idiots like myself won't accidentally remove important objects in their router.
My concrete scenario: an RB2011UiAS router used in my home with a "main LAN bridge" interface and 90% of physical ports attached to it.
I was intending to click on Torch to do some diagnostics, but instead clicked Remove.
This effectively deleted my LAN and prevented me from reconnecting to the router (and also caused mild panic).
I don't think an "are you sure" confirmation is the right way to go, as people just click though without reading them.
Instead, force users to remove dependencies before an object is removable.
In my particular scenario, if I really wanted to remove my "main LAN bridge" I'd need to first unbind all IP addresses and DHCP server from the interface, and then remove all ports from it.
I understand every object in RouterOS would require different rules, but perhaps prioritise things which have more serious consequences (eg: removing things that the current Winbox connection depends on).
Possible alternative: an undo stack (although that wouldn't have helped in my scenario).
And a tale of woe if anyone is interested: https://blog.ligos.net/2018-02-18/Mikro ... utton.html
Thanks in advance.
Murray