Naming a Query makes it lose its UI function

Open
#1,487 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Domain
frontend

Research direction

Start by locating the query naming and rendering entry points, then reproduce the issue by naming a Query and checking whether its UI controls disappear. The report names no files or tests, so first trace how named and unnamed Queries are displayed. Done means a named Query retains its UI controls and can still be changed through the UI.

Written by the indexing model from the issue text.

Description

Search first
  • I searched and no similar issues were found
What Happened?

If you name a Query it loses its UI and become only text code. You can't change it using the UI anymore because there are not buttons. Shouldn't it keep its UI functionality even after naming it?

Reproduce the Bug

Read above.

Expected Behavior

The Query should keep its UI form/elements after naming it.

Screenshots

No response

Files

No response

Browser, Desktop or Mobile Platform Information

No response

Additional Context

No response

Are you willing to submit a PR? If you know how to fix the bug.
  • I'm willing to submit a PR (Thank you!)
Dominant language
No language data
Stars
29
Forks
2
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 logseq/db-test

All issues in logseq/db-test

Similar issues

More Web Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.