From fb089ae297b27f51777318e3a28bca8b172a4165 Mon Sep 17 00:00:00 2001 From: Ivan Gabaldon Date: Tue, 2 Dec 2025 10:18:00 +0000 Subject: [mod] client/simple: client plugins (#5406) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * [mod] client/simple: client plugins Defines a new interface for client side *"plugins"* that coexist with server side plugin system. Each plugin (e.g., `InfiniteScroll`) extends the base `ts Plugin`. Client side plugins are independent and lazy‑loaded via `router.ts` when their `load()` conditions are met. On each navigation request, all applicable plugins are instanced. Since these are client side plugins, we can only invoke them once DOM is fully loaded. E.g. `Calculator` will not render a new `answer` block until fully loaded and executed. For some plugins, we might want to handle its availability in `settings.yml` and toggle in UI, like we do for server side plugins. In that case, we extend `py Plugin` instancing only the information and then checking client side if [`settings.plugins`](https://github.com/inetol/searxng/blob/1ad832b1dc33f3f388da361ff2459b05dc86a164/client/simple/src/js/toolkit.ts#L134) array has the plugin id. * [mod] client/simple: rebuild static --- searx/engines/piped.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'searx/engines/piped.py') diff --git a/searx/engines/piped.py b/searx/engines/piped.py index e9585eae1..249540c38 100644 --- a/searx/engines/piped.py +++ b/searx/engines/piped.py @@ -40,8 +40,8 @@ Known Quirks The implementation to support :py:obj:`paging ` is based on the *nextpage* method of Piped's REST API / the :py:obj:`frontend API `. This feature is *next page driven* and plays well with the -:ref:`infinite_scroll ` setting in SearXNG but it does not really -fit into SearXNG's UI to select a page by number. +:ref:`infinite_scroll ` plugin in SearXNG but it does not +really fit into SearXNG's UI to select a page by number. Implementations =============== -- cgit v1.2.3