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

`#Asset` label is not displayed on asset nodes when `Hide from Node` is disabled

Open Beginner friendly
#1,452 0 comments 0 reactions 0 assignees View on GitHub

@tiensonqin is already working on this.

Since Oct 18, 2026.

  • #13799 by @tiensonqin — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Domain
frontend

Research direction

Open the #Asset tag page, disable Hide from Node, and inspect an asset node to reproduce the missing label. Trace how that setting controls tag labels on nodes and compare with another tag if useful. Done means #Asset appears on asset nodes when the option is disabled.

Written by the indexing model from the issue text.

Description

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

The #Asset label is not displayed on asset nodes even when the Hide from Node option is disabled for the #Asset tag.

Reproduce the Bug
  1. Open the #Asset tag page.
  2. Disable the Hide from Node option.
  3. Check an asset node.
Expected Behavior

The #Asset label should be displayed on asset nodes when Hide from Node is disabled.

Screenshots

No response

Files

No response

Browser, Desktop or Mobile Platform Information

windows11
logseq 2.0.2

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
28
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.