feat: show full NFT metadata fields with raw JSON toggle on token page

Open
#75 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
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
react
Domain
frontend

Research direction

Start at the NFT token page entry point and inspect how token.metadata, the attributes card, and metadata_status are currently exposed. Add the Metadata section with formatted and raw modes, then verify that excluded fields, null metadata, and non-fetched metadata follow the stated visibility rules.

Written by the indexing model from the issue text.

Description

enhancement

Problem

NFT token page only surfaces image, description, and attributes. All other metadata fields (custom properties, rarity scores, external_url, animation_url, etc.) are silently ignored. No way to inspect raw metadata JSON.

Proposed Solution

Add a Metadata section below the attributes card on the NFT token page with two modes:

Formatted view (default)
  • Render every key/value pair from token.metadata dynamically
  • Skip already-displayed fields: image, image_url, imageUrl, image_data, description, attributes
  • Format values: strings as text, numbers as monospace, URLs as anchor links, objects/arrays as pretty-printed JSON blocks
  • Section header: "Metadata" with a toggle button
Raw JSON view (toggle)
  • Switch button (e.g. "Formatted / Raw") in the section header
  • Renders JSON.stringify(token.metadata, null, 2) in a scrollable <pre> block with monospace font
UX details
  • Toggle state: useState local, default to formatted
  • Only show section when token.metadata !== null
  • Hide section when metadata_status !== 'fetched'
Dominant language
Rust
Stars
2
Forks
1
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 evstack/atlas

All issues in evstack/atlas

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.