Enable JSON viewer for .pipeline files
See original GitHub issueIs your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I’m always frustrated when […]
Currently .pipeline
files can only be opened in the VPE or the plain text editor from the File Browser context menu:
Describe the solution you’d like
Enable the JSON viewer (like it is for Jupyter notebooks) to make it easier to browse the file:
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
JSON formatting with jq and CI/CD linting automation | GitLab
Learn how to filter in JSON data structures and interact with the REST API. Use the GitLab API to lint your CI/CD configuration...
Read more >Build Steps from Json Plugin
From JSON - the value you'll assign for 'Parameter value' will be looked for in the JSON file you specified for the 'Path...
Read more >Define a Pipeline in JSON Format
Copy data from Amazon S3 to Amazon Redshift using the full pipeline definition JSON file.
Read more >JSON Formatter - SnapLogic Documentation - Confluence
In this pipeline, the JSON Formatter Snap, creates a file with a header value on a specified location. The metadata is passed to...
Read more >JSON data size fix - Designing Pipelines
I enabled the json lines in JSON FORMATTER snap… after which my file could open up faster in notepad++. Awesome! Worked for me!...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Once https://github.com/elyra-ai/elyra/pull/2495 is merged this should be pretty trial for me to fix
IIUC https://github.com/jupyterlab/jupyterlab/pull/11540 has added support for this. Once that is released we’ll be able to add this support. As such moving this to the 4.0 sprint (with the assumption that it will be release in lab 4)