Filter Functions

Abierto
  • ¿Algo no está bien?
#673 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
40/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
python
Área
databases, frontend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Python
Estrellas
37
Forks
17
Merge medio
16 h 7 min
PR fusionados (30 d)
128

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de OpenSAK-Org/OpenSAK

Todos los issues de OpenSAK-Org/OpenSAK

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.