UCI option vs list

For Developers
1

I remember that in the past, if a configuration option was meant to be a list, passing option would work anyway.

With the latest openwrt 24.10 version, it seems that if option is passed when it should be a list, UCI ignores it silently without any warning.

I wanted to ask here if you are aware of this and if you think it's a good idea?
I think the fact that previous versions were more forgiving was a nice feature, rather than a bug.
I also think that changing this behavior in this way without making it issue any syslog warning makes it harder to discover.

2

Can you give a working example? I'm curious what the context is in which this happens, cli, shell (i.e., the '*foreach' functions in /lib/functions.sh), LuCI API, all?

3

IDK. For me (6.12 Main), any add or add_list or any invalid entry always seemed to return me to the --help screen.

This is what I get:

root@RuralRoots:~# uci add dhcp.@dnsmasq[0].dhcp_option='6,10.10.1.254'         # invalid use of a list option
Usage: uci [<options>] <command> [<arguments>]

Commands:
        batch
        export     [<config>]
        import     [<config>]
        changes    [<config>]
        commit     [<config>]
        add        <config> <section-type>
        <truncated>

root@RuralRoots:~# uci add_list dhcp.@dnsmasq[0].dhcp_option='6,10.10.1.254'    # Silent
root@RuralRoots:~# uci show dhcp
dhcp.@dnsmasq[0]=dnsmasq
dhcp.@dnsmasq[0].domainneeded='1'
dhcp.@dnsmasq[0].dhcp_option='6,10.10.1.254'                                    # and here's the un-commited option