Componentize REPL

Open
#70 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
fsharp

Research direction

Start by reviewing the continuation issue at repl-legacy/issues/42 and the component list in this issue. Examine how the F# compiler and Fable bundle, worker, metadata and REPL library, Monaco integration, and UI are currently separated. Done means documenting an agreed plan for which parts belong in an embeddable package.

Written by the indexing model from the issue text.

Description

Continuation of https://github.com/fable-compiler/repl-legacy/issues/42

I renamed the repositories. @citymeterio It's probably better if you remove your local copy and clone fable-compiler/repl again.

We should write down a plan to make it easier to embed the REPL in other webs. These are the different parts composing the REPL currently, should all go into the package or only some of them?

  • F# compiler + Fable bundle: This is generated in the Fable CI server (AppVeyor)
  • Worker: prevents locking the UI and contains some helpers to communicate with the Fable bundle
  • Metadata + Fable REPL library: The REPL needs to load several netstandard dlls to compile F# code
  • Monaco integration: Tooltip, go to definition, autocompletion... providers
  • UI
Dominant language
F#
Stars
68
Forks
36
Avg merge
13h 1m
Merged PRs (30d)
2

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.

More from fable-compiler/repl

All issues in fable-compiler/repl

Similar issues

More Web Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.