HAproxy-Devel config GUI bug

MrPete

A subtle bug discovered in the backend config:
Assume a typical use of HAproxy to select among several web server names, using ACL's and actions.

Note that you can NOT do this all in a single command (at least the way it is interpreted right now)

If you define multiple options in a single ACL, it seems that ought to work...
Because while each action specified can be tied to a specific ACL option...
... If you do that, you get an error.

So, I create a separate ACL+action pair for each option. If everything is configured just-so, it does work correctly.
Here is an easy typo, that could be caught in the GUI, but causes no error until compile time, and requires some head-scratching to decipher:

Set up ACL "xyz" on host matching xyz.example.com
Set up action underneath (obviously tied to that ACL) to use server xyz
Save... set up other ACL's...
This one causes a compile error, because a crucial field was left blank.
"Condition ACL names" must be filled in by manually typing "xyz" to match the ACL name "xyz" above.

That cannot be left blank. ALWAYS generates an error because the config produced is "use-server xyz" which is not allowed. MUST say "use-server xyz if xyz"

So. Why not either auto-fill, or have a dropdown to select from available ACL's, or give an error if left blank?