Filter Functions

オープン
#673 コメント 2 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
3/5
見積もり時間
1〜2日
初心者へのやさしさ
40/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
静か
技術スタック
python

調査の方向性

The issue concerns the "all in filter" option for delete, move and copy of caches in the Waypoint actions, which currently acts on the whole database when no filter is set. Start by finding where that option reads the active filter state and reproduce it with no filter applied. Done means that with no filter the option is disabled or shows a "No filter set" message and changes nothing, and that an explicit choice for all caches in the database exists. The maintainer has not chosen between the two proposed behaviours, so confirm the approach in the thread first.

索引モデルが issue の本文から書いたものです。

説明

area: filters improvement
Current State

This may duplicate some issues already open but wanted to talk about how the filter option could be improved using certain built in options. Right now, through Waypoint we have the ability to delete, move or copy caches from one database to another using, selected caches, flagged caches and all in filter. When selecting all in filter it seems OSAK assumes that if no filter is active, "all in filter" is all in database. This seems confusing from my workflow point of view. If the filter box shows none, then no filter is set. If I select the delete, move or copy "all in filter" option I am assuming I have a filter set. Nothing should be done if no filter is set using that option.

Proposed Improvement

If no filter is set the option "all in filter" should be grayed out or a popup screen should say "No filter set" and not perform anything for all of the caches in the database. Also add a choice to do these functions for all caches in the databases.

Expected Benefits

This would avoid performing something to all caches in your database thinking you have a filter set.

主要言語
Python
スター
37
フォーク
17
平均マージ
16時間 7分
マージ済み PR(30日)
128

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

OpenSAK-Org/OpenSAK のほかの issue

OpenSAK-Org/OpenSAK の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。