`reflex cloud project list` table renders `tier` as a raw JSON blob

Open Beginner friendly

#7,300 opened on Sep 24, 2026 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 2/5
Estimated time: 1-3 hours
Newbie friendliness: 75/100

Issue type: Bug
Clarity: Clearly specified
Activity status: Active
Tech stack: python
Domain: cli

Research direction

Look at the reflex-hosting-cli package, specifically the table rendering logic for reflex cloud project list. The tier field is an object being printed as raw JSON. Find where the table is formatted (likely in a command file or output module) and modify it to display only the 'name' property of the tier object. Also check apps inspect and apps history for similar nested object handling. Test by running the CLI command to see the readable output.

Written by the indexing model from the issue text.

Description

Package: reflex-hosting-cli (reproduced on main at ea035ea47 and on #7207 at 988718e78)

The tier field is an object ({"name": "Enterprise", "cpu_quota": 100.0, "ram_quota": 500.0, "deployment_quota": 100}). The text table prints it as serialized JSON, which wraps into a tall, unreadable cell and squeezes every other column:

$ reflex cloud project list
┏━━━━━━━━━━┳━━━━━━━━━━┳━━━━━━━━━━┳━━━━━━━━━━━┳━━━━━━━━━━┳━━━━━━━━━━━┳━━━━━━━━━━┓
┃ id       ┃ name     ┃ tier     ┃ app_count ┃ deploym… ┃ cpu_usage ┃ memory_… ┃
┡━━━━━━━━━━╇━━━━━━━━━━╇━━━━━━━━━━╇━━━━━━━━━━━╇━━━━━━━━━━╇━━━━━━━━━━━╇━━━━━━━━━━┩
│ b32eac0… │ other_p… │ {"name": │ 1         │ 1        │ 1.0       │ 1.024    │
│          │          │ "Enterp… │           │          │           │          │
│          │          │ "cpu_qu… │           │          │           │          │
│          │          │ 100.0,   │           │          │           │          │
...

apps inspect (latest_deployment) and apps history on main (vm type) show nested objects the same way.

Expected: show the tier name only (e.g. Enterprise), or flatten it into readable columns. Leave the full object to --json.

Dominant language: Python
Stars: 28.9k
Forks: 1.8k
Avg merge: 1d 15h
Merged PRs (30d): 180

Contributor guide

Open the contributing guide

First steps

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

Similar issues

docs: update workflows.md for slide deck Node test discovery Open

agent-ready documentation needs-triage

Difficulty 1/5 1-3 hours Newbie friendliness 88/100

microsoft/hve-core#3012 · Opened Sep 25, 2026
config_keys.rst says every result file PyBNF writes is alphabetical, but the credible-interval files and start_point.txt use declaration order Open

documentation

Difficulty 1/5 Under an hour Newbie friendliness 91/100

lanl/PyBNF#932 · Opened Sep 25, 2026
workflow-status page template still says reusable workflows are "triggered only by workflow_call:" Open

Difficulty 1/5 Under an hour Newbie friendliness 92/100

LearningCircuit/local-deep-research#6804 · Opened Sep 24, 2026
Add https://search.jeremyh.xyz/ Open

instance instance add

Difficulty 1/5 Under an hour Newbie friendliness 72/100

searxng/searx-instances#939 · 1 comment · Opened Sep 24, 2026
Azure Sandboxes: Small and ExtraSmall tiers always fail to deploy (disk request exceeds tier maximum) Open

area-deployment area-integrations triage:bot-seen

Difficulty 2/5 Half a day Newbie friendliness 86/100

microsoft/aspire#20459 · 1 comment · Opened Sep 24, 2026

More Python issues