ProxymanApp / ProxymanApp/Proxyman
Request: Formatted Response Body in Exported Files
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 7k
- Forks
- 237
- PR merge metrics
- No merged PRs in 30d
Description
Description
The exported Response body is not formatted, unlike the formatted view in the preview interface. This inconsistency creates extra work for users who need to manually format the exported data.
Why this feature/change is important?
-
Time-saving: Users won't need to reformat the exported data manually, saving significant time, especially for those who frequently export and analyze response data.
-
Consistency: It ensures consistency between what users see in the preview and what they get in exported files, improving overall user experience.
-
Ease of analysis: Formatted data is much easier to read and analyze, enabling users to work more efficiently with the exported information.
-
User flexibility: Adding a formatting option during export would cater to different user preferences, allowing them to choose between formatted and unformatted output as needed.
This enhancement would greatly improve the usability of Proxyman, especially for users who rely on exporting data for further analysis or documentation.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by comparing the preview interface's formatted Response body with the export flow described in the issue. Determine where export formatting is handled and how users should choose formatted or unformatted output; done means exported files match the preview when formatting is selected while preserving the unformatted option.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100