Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

ux(redis): clicking the selected database in the tree does not leave an open key

Open Beginner friendly
  • Is something wrong?
#1,837 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
79/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
dart, flutter, redis
Domain
database

Research direction

Start in MainScreenNavigator at the Redis database selection’s same early return, then trace how the Redis explorer tracks an open key. Reproduce the flow by selecting db0, opening a key, and clicking db0 again. Done when that click restores the key list, matching the stated behavior for the breadcrumb and other overview selections.

Written by the indexing model from the issue text.

Description

bug P3 ux
Problem

Found driving a debug build against the docker Redis. Open Local Redis → Databases → db0 (the key list shows), then open a key (e.g. querya:stream:events). The tree still highlights db0. Clicking db0 again does nothing: the key stays open and the list does not come back. Only the breadcrumb (Local Redis › db0) goes back.

The same shape as #1820 / the tree's "same selection" guard: choosing the node that is already selected is dropped, but here the workspace shows something deeper than the selected node.

Expected

Clicking the highlighted database returns to its key list, as clicking a table's schema or the server row returns to the overview.

Where

MainScreenNavigator (the Redis database selection: the same early return) and the Redis explorer's open-key state.

Dominant language
Dart
Stars
23
Forks
1
Avg merge
45m
Merged PRs (30d)
529

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from QueryaHub/Querya-Desktop

All issues in QueryaHub/Querya-Desktop

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.