infinitered / infinitered/reactotron

Confusing UI change between 2.17 and 3.7

Open
#1,449 0 comments 2 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
15.6k
Forks
972
PR merge metrics
No merged PRs in 30d

Description

### Describe the bug

Inbetween version changes, it seems like the rendering logic for request bodies changed a little bit. In the following two screenshots, you see the exact same request being made, but being rendered differently:

### 2.17:
![image](https://github.com/infinitered/reactotron/assets/22714514/ecaaf4e8-1c3d-47e7-bb78-b4d8443f03b0)

### 3.7:
![image](https://github.com/infinitered/reactotron/assets/22714514/09b349df-a476-4108-ad55-310b5c4cf53f)

I think the new version is a bit confusing, since it makes the request body look like it's a `FormData`, and not a `JSON`. It caused some headache for me and my coworkers :D

### Reactotron version

3.7.0

Contributor guide

Open the contributing guide

Research direction

Compare the request-body rendering shown in the 2.17 and 3.7 screenshots, then trace the desktop UI code responsible for displaying request bodies. Done means a JSON request body is clearly presented as JSON rather than appearing to be FormData.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
desktop, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.