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

[Enhancement] Wikipedia Metadata: Section Whitelist #129

Open
MrWheyne opened this issue Jan 19, 2025 · 0 comments
Open

[Enhancement] Wikipedia Metadata: Section Whitelist #129

MrWheyne opened this issue Jan 19, 2025 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@MrWheyne
Copy link

Is your feature request related to a problem? Please describe.
Currently the Wikipedia Metadata plugin features a blacklist for sections users might like to omit when fetching description text. While this is nice and works as intended, it creates some problems when users are just interested in specific sections like Gameplay or Plot. Because there's no universal convention (at large) as to how sections should be titled, and due to how sometimes there's just not enough information to fill multiple different sections, article writers tend to merge topics together into a single section. Because the blacklist does not (and probably should not) support fuzzy matching, users end up having to repeat the same words multiple times:

Image

Describe the solution you'd like
Add an option for a whitelist (just like proxy servers do), where the plugin will instead only fetch sections which include the words added (and the page overview, obviously) and ignore everything else. Because this will result in the plugin only fetching the page overview if no section is added, leave the blacklist as the default option so the plugin still has a way to fetch the entire page for users who prefer it that way. Also, because the clear whitelist would have the same effect as the checkbox "Only use overview of the wiki page as description", that could be repurposed to be the toggle between blacklist or whitelist function.

Describe alternatives you've considered
This, I believe it the most practical solution I could come up with, and one I think will not take much development effort to implement, since it's basically the same logic, only reversed.

Additional context
None, but I'm open if any questions might arise.

@MrWheyne MrWheyne added the enhancement New feature or request label Jan 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants