All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
Oh look, another minor release.
-
The
unique_bangs
plugin option. This indicates whether the database should remove bangs with duplicate URLs and very useful for removing aliases from cluttering the search results.
-
The description of the plugin metadata keeping up with the recent convention.
-
The database has been reworked. This shouldn’t affect end users overall. [1]
I don’t think this is a good application of "Release early, release often" but there are minor behavior changes for the plugin. Which means a new version of the plugin.
-
The plugin can now only accept one bangs database file at a time.
-
force_download
default value fromtrue
tofalse
due to fixed behavior.
Main highlight of this release is the addition of plugin-specific configuration.
It should be located in $POP_PLUGIN_PATH/bangs/config.json
.
Unlike the bangs database, the configuration is not merged between different plugin paths.
-
A plugin-specific configuration file.
-
force_download
(boolean) lets you configure to force download of database file when missing. -
max_limit
(number) indicates the maximum number of search results to be returned. -
db_url
(string) points to the URL of the default bangs database used together withforce_download
. -
default_bangs
(array[string]) is a list of bangs to be used when no bangs are found from the search query; handy for quicker search especially when you’re used to searching with your default search engine of choice.
-
-
Return the search results sorted by relevance when in the launcher service. [2]