OpenFn / OpenFn/lightning

Sort Keys Alphabetically in the JSON Viewer

Open
#3,991 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

new feature
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.

Image
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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.