OpenFn / OpenFn/lightning

Inspector: Report run errors in Monaco directly

Open
#2,805 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Elixir
Stars
296
Forks
86
Avg merge
1d 13h
Merged PRs (30d)
50

Description

When the inspector is open on a run, if the current step had an error, we should report that error in the margin in the Monaco editor.

Monaco provides an API for this stuff and the new error reporting in the runtime gives us accurate positions and (hopefully) good error messages.

This may require support at the lightning end (we probably need to report error positions in step-complete)

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 by tracing the inspector's run handling and the runtime's step-complete event, then identify how Monaco receives diagnostics. Done means a current-step error appears in the Monaco margin with the runtime-provided position and message, including any required step-complete support.

Written by the indexing model from the issue text.

Assessment

Tech stack
elixir
Domain
full-stack
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.