Implement Monaco editor across board
Open
Nobody has claimed this yet.
Epic
ux/ui improvement
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
We have recently made improved the user experience for loading I/O clips in the editor by implementing the Monaco editor. This should also be implemented across the app where applicable:
Currently, here are the places this should be done:
- Create input data clip and job expression interface
- Data clip viewer
- Path condition expression
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 locating the existing Monaco editor implementation used for loading I/O clips, then compare the create input data clip and job expression interface, data clip viewer, and path condition expression. Done means Monaco is implemented in each applicable location with the intended editor experience shown in the issue images.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100