Add an exception list option to the preferred external downloader

Open
#640 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
dart
Domain
mobile

Research direction

Start by locating the existing preferred external downloader setting and the download-selection flow it affects. Review how WebLibre currently chooses between its internal and external downloaders, then identify where host exceptions should be configured. Done means users can add host exceptions and downloads from those hosts retain the normal downloader choices while other downloads use the preferred external downloader.

Written by the indexing model from the issue text.

Description

enhancement P3

The new “choose external downloader as preferred downloader” option is a very useful addition.

It would be great if this setting could also have an exception list for specific sites/hosts.

For example, I may want to use an external downloader as the preferred downloader in general, but for:

"drive.usercontent.google.com"

I may want WebLibre to not prefer the external downloader and instead keep its normal download behavior, including the usual internal/external downloader choices.

The 1DM Integration Module extension currently provides this functionality through its site exception list. Adding a similar exception list to WebLibre would cover the remaining part of the extension that I use.

For example:

Preferred downloader: External downloader
Exceptions:
"drive.usercontent.google.com"
"example.com"

This would allow users who currently use the 1DM Integration Module for this functionality to remove the extension entirely and have the functionality built directly into WebLibre.

Thanks for considering it!

Screenshot of 1DM Integration Module extension 👇

Image
Dominant language
Dart
Stars
1k
Forks
41
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from FaFre/WebLibre

All issues in FaFre/WebLibre

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.