Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What's the difference between "postprocessors" and "postprocsesor" in the config file #6770

Closed
a84r7a3rga76fg opened this issue Jan 4, 2025 · 3 comments

Comments

@a84r7a3rga76fg
Copy link

I've been using postprocessor this whole time. But the current default config says postprcessors. Should I change it to that? Also, I keep mine at the bottom of the config file, will that change anything?

"postprocessors": null,

@Hrxn
Copy link
Contributor

Hrxn commented Jan 6, 2025

Change? These are two different things and they will behave differently.
"postprocessor" is its own section of a config file, you can define different post-processors there while also assigning them to a name.

"postprocessors" on the other hand are part of the options of a specific extractor. You can activate usage of a post-processor here defined in their section of the config by just referencing their by name.

It's just a nice convenience feature. You can completely ignore "postprocessor", although the benefit of a referenced post-processor here is that you can simply make all changes you want in one spot, and don't have to copy and paste your post-processor setup all across your own config file.

@a84r7a3rga76fg
Copy link
Author

Which specific extractor is line 14 in?

@mikf
Copy link
Owner

mikf commented Jan 8, 2025

None in particular, as it is in the general "extractor" part. Any post processors listed there would be run for all extractors.


#6582 (comment) is an example of postprocessor -> postprocessors usage.

@mikf mikf closed this as completed Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants