Feature request: Parse URI should support outputting as JSON
- Dominant language
- JavaScript
- Stars
- 35.8k
- Forks
- 4.1k
- Avg merge
- 2d 26m
- Merged PRs (30d)
- 33
Description
**Is your feature request related to a problem? Please describe.**
To make it easier to build recipes based on output from the Parse URI feature, please add a checkbox setting so that it outputs the result as JSON.
**Describe the solution you'd like**
A checkbox setting in Parse URI that formats the output as JSON, as described below:
Input:
```
https://www.google.com/search?q=test&sourceid=chrome&ie=UTF-8
```
Before:
```
Protocol: https:
Hostname: www.google.com
Path name: /search
Arguments:
q = test
sourceid = chrome
ie = UTF-8
```
After (with the JSON checkbox checked):
```
{
"Protocol":"https:",
"Hostname":"www.google.com",
"Path name":"/search",
"Arguments": {
"q" : "test",
"sourceid" : "chrome",
"ie" : "UTF-8"
}
```
Contributor guide
Research direction
Start at the Parse URI operation and its existing settings and output handling. Add a JSON output checkbox whose result matches the requested structure, then verify the setting with the sample URI and confirm the default output remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100