Sort Keys Alphabetically in the JSON Viewer
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
Description
When reviewing workflow runs, it would be much easier to inspect the Input/Output JSON if the keys could be sorted alphabetically. This would make it simpler to find specific fields quickly, especially in large or nested payloads.
Right now, the JSON viewer shows keys in their raw order, which can take more time to scan through.
Proposed Solution
Add support for alphabetically sorting all keys in the JSON viewer to make the data easier to read. A built-in sorting option would work, as long as users can view the JSON in alphabetical order when needed.
Why This Would Help
- Makes it faster to locate specific fields
- Helpful for QA, consultants, and developers working with bigger payloads
- Supports clearer debugging and structure verification
- Aligns with how many other JSON viewers handle key sorting
Acceptance Criteria
- JSON keys can be sorted alphabetically for display
- Sorting applies across all nesting levels
- The actual data is not changed, sorting is only for the viewer
https://openfn.slack.com/archives/C0394D0GBUN/p1762782943119009
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 at the JSON viewer used for workflow-run Input/Output data and trace how nested payloads are rendered. Confirm that alphabetical ordering applies at every nesting level while leaving the underlying data unchanged; verify the viewer displays the expected order for large and nested JSON payloads.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100