ibox = 'Infobox - whatever' fixes['add-infobox'] = { 'regex': True, 'exceptions': { 'text-contains': [ r'\{\{' + first_upper(ibox), r'\{\{' + first_lower(ibox), ], }, 'msg': { '_default': 'add infobox', }, 'replacements': [ build_infobox_regex(ibox), ], }
My text-contains key includes some regexes and the fix has regex: True. However, those exceptions only skip relevant articles when I include -regex to the command (which is otherwise redundant if I only use fixes).
Because Exceptions specified via 'fix' are merged to those via CLI.
So all exceptions become common,
And when this is done, the 'regex': True information is not considered, but only the -regex value.
I am not sure what is the wanted behaviour.
And if there is a reason in not handling the exceptions fix by fix.
Replacement management in replace.py gives me a headache.
Me too after your clarification. But I believe we can handle that.
There is just a few scenarios: (pwb.py replace only run with...)
My opinion:
Now there's only one remaining point: combined input. I would introduce a new -inherit argument that would optionally make all command line exceptions inherited to all fixes (as well as the "squashed" one), otherwise (default behavior) it would only be relevant for command line replacements.
Comments?
If I got you correctly, I agree.
Each fix (either via user-fixes or cmd line) has its own set of specs (we can see cmd line inputs as 'one fix').
An option from cmd line to override fix definition in specific areas.