From 211089bead477ddbc6a6a73c4fa4bffb38bc78e3 Mon Sep 17 00:00:00 2001 From: arabcoders Date: Sat, 25 Oct 2025 20:05:24 +0300 Subject: [PATCH] minor fixes to file listing, and unifiy how we present tips --- ui/app/pages/browser/[...slug].vue | 24 ++++++++++++--- ui/app/pages/conditions.vue | 45 +++++++++++++++------------- ui/app/pages/notifications.vue | 48 ++++++++++++++++-------------- ui/app/pages/presets.vue | 8 +++-- ui/app/pages/settings.vue | 1 + ui/app/pages/tasks.vue | 24 +++++++++++---- 6 files changed, 93 insertions(+), 57 deletions(-) diff --git a/ui/app/pages/browser/[...slug].vue b/ui/app/pages/browser/[...slug].vue index 64f47c78..f089eefa 100644 --- a/ui/app/pages/browser/[...slug].vue +++ b/ui/app/pages/browser/[...slug].vue @@ -145,7 +145,8 @@ style="min-width: 1300px; table-layout: fixed;"> - + #
- -
    -
  • Filtering is based on yt-dlp’s --match-filter logic. Any expression that works with yt-dlp - will also work here, including the same boolean operators. We added extended support for the OR - ( || ) operator, which yt-dlp does not natively support. This allows you to combine multiple - conditions more flexibly.
  • -
  • - The primary use case for this feature is to apply custom cli arguments to specific returned info. -
  • -
  • - For example, i follow specific channel that sometimes region lock some videos, by using the following - filter i am able to bypass it availability = 'needs_auth' & channel_id = 'channel_id'. - and set proxy for that specific video, while leaving the rest of the videos to be downloaded normally. -
  • -
  • - The data which the filter is applied on is the same data that yt-dlp returns, simply, click on the - information button, and check the data to craft your filter. You will get instant feedback if the - filter matches or not. -
  • -
-
+
+
+
    +
  • Filtering is based on yt-dlp’s --match-filter logic. Any expression that works with yt-dlp + will also work here, including the same boolean operators. We added extended support for the + OR ( || ) operator, which yt-dlp does not natively support. This allows you to combine + multiple conditions more flexibly. +
  • +
  • + The primary use case for this feature is to apply custom cli arguments to specific returned info. +
  • +
  • + For example, i follow specific channel that sometimes region lock some videos, by using the following + filter i am able to bypass it availability = 'needs_auth' & channel_id = 'channel_id'. + and set proxy for that specific video, while leaving the rest of the videos to be downloaded normally. +
  • +
  • + The data which the filter is applied on is the same data that yt-dlp returns, simply, click on the + information button, and check the data to craft your filter. You will get instant feedback if the + filter matches or not. +
  • +
+
+
diff --git a/ui/app/pages/notifications.vue b/ui/app/pages/notifications.vue index 9aedad56..9b2aa625 100644 --- a/ui/app/pages/notifications.vue +++ b/ui/app/pages/notifications.vue @@ -156,7 +156,7 @@

- {{ item.request.headers.map(h => h.key).join(', ') }} + {{item.request.headers.map(h => h.key).join(', ')}}

@@ -193,28 +193,30 @@
- -
    -
  • - When you export notification target, We remove Authorization header key by default, - However this might not be enough to remove credentials from the exported data. it's your responsibility - to ensure that the exported data does not contain any sensitive information for sharing. -
  • -
  • - When you set the request type as Form, the event data will be JSON encoded and sent as - ...&data_key=json_string, only the data field will be JSON encoded. - The other keys id, event and created_at will be sent as they are. -
  • -
  • We also send two special headers X-Event-ID and X-Event with the request.
  • -
  • - If you have selected specific presets or events, this will take priority, For example, if you limited the - target to default preset and selected ALL events, only events that reference the - default preset will be sent to that target. Like wise, if you have limited both events and - presets, then ONLY events that satisfy both conditions will be sent to that target. Only the - test events can bypass these conditions. -
  • -
-
+
+
+
    +
  • + When you export notification target, We remove Authorization header key by default, + However this might not be enough to remove credentials from the exported data. it's your responsibility + to ensure that the exported data does not contain any sensitive information for sharing. +
  • +
  • + When you set the request type as Form, the event data will be JSON encoded and sent as + ...&data_key=json_string, only the data field will be JSON encoded. + The other keys id, event and created_at will be sent as they are. +
  • +
  • We also send two special headers X-Event-ID and X-Event with the request.
  • +
  • + If you have selected specific presets or events, this will take priority, For example, if you limited the + target to default preset and selected ALL events, only events that reference the + default preset will be sent to that target. Like wise, if you have limited both events and + presets, then ONLY events that satisfy both conditions will be sent to that target. Only the + test events can bypass these conditions. +
  • +
+
+
diff --git a/ui/app/pages/presets.vue b/ui/app/pages/presets.vue index f90b16c9..b3d9e63d 100644 --- a/ui/app/pages/presets.vue +++ b/ui/app/pages/presets.vue @@ -186,11 +186,13 @@
- -

When you export preset, it doesn't include the cookies field contents for security +

+

+ + When you export preset, it doesn't include the cookies field contents for security reasons.

- +
diff --git a/ui/app/pages/settings.vue b/ui/app/pages/settings.vue index c0b8868a..768d1811 100644 --- a/ui/app/pages/settings.vue +++ b/ui/app/pages/settings.vue @@ -264,6 +264,7 @@