untested fix for bug introduced by fix for #67 #101
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I am not sure I agree that #67 was a bug -- I kind of liked having "All" and "Virtual combination" at the top (not that I ever use that interface...).
That aside, the fix for #67 introduced a bug, in that (nearly) all the option values are blank, which means the database is stuck on "All" and you can't change it. This is because the language name is used as a key into the %Db hash to look up the option value, but once the language name is trimmed, the hash lookup breaks. This bandaid fix keeps the untrimmed value around for use in the foreach loop (in a civilized language, we'd use zipWith :) ).
I don't have a running instance of jbovlaste so obviously this fix hasn't been tested. I "tested" it in a REPL with fake data, but I don't know what the real data looks like. And I don't know Perl, so YMMV.
I also fixed the indentation of the Strategy and Database loops.