Rafał Miłecki e7c9c63c65 luci-mod-network: split config migration into 2 steps ... Problem with handling all migrations in 1 step is that uci.sections() doesn't include changes queued using uci.callAdd() and uci.callSet(). That could result in unexpected behaviour and generating invalid configs. For the sake of simplicity and reliability use 2 steps migration. The downside is that users may get prompted twice to migrate. Reported-by: Hauke Mehrtens <hauke@hauke-m.de> Fixes: 74be304e54 ("treewide: use "device" option in UCI "interface" sections") Signed-off-by: Rafał Miłecki <rafal@milecki.pl> Tested-by: Hauke Mehrtens <hauke@hauke-m.de>		2021-05-29 18:19:14 +02:00
..
dhcp.js	Merge pull request #4709 from opastushkov/dnsmasq_crash_on_duplication_of_static_ip	2021-03-17 08:55:09 +01:00
diagnostics.js	treewide: transition div tables to actual table markup	2020-11-27 21:36:40 +01:00
hosts.js	treewide: import utility classes explicitly	2020-04-03 10:00:06 +02:00
interfaces.js	luci-mod-network: split config migration into 2 steps	2021-05-29 18:19:14 +02:00
routes.js	luci-mod-network: fix reading static route table value	2020-05-13 17:20:05 +02:00
switch.js	treewide: import utility classes explicitly	2020-04-03 10:00:06 +02:00
wireless.js	luci-mod-network: allow wifi bridging with bridge or bridge vlan ifaces	2021-03-18 17:28:40 +01:00