Skip to content

Conversation

@drebs
Copy link

@drebs drebs commented Aug 23, 2024

Filter objects must be initialized with the options found in the config file but, in the case of --enable-filters, objects were being re-initialized and config options ignored.

This change makes use of the configured_filter_chain list of already-initialized filter objects and trims it down by comparing filter class names with the values passed in the command line for --enable-filters.

Closes: #40

Filter objects must be initialized with the options found in the config file
but, in the case of `--enable-filters`, new objects were being initialized with
config options ignored.

This change makes use of the `configured_filter_chain` list of
already-initialized filter objects and trims it down by comparing filter class
names with the values passed in the command line for `--enable-filters`.

Closes: afewmail#40
@drebs drebs force-pushed the fix-enable-filters branch from ee930db to 841b78e Compare August 27, 2024 09:48
@GuillaumeSeren
Copy link
Collaborator

Hey @drebs ,
thank you for this patch.

My feeling is if you command override some option you expect it to ignore the config file,
but I may be wrong please elaborate a bit on the use case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Configuration is not took in account when using --enable-filters

2 participants