Figure out some way of having predefined or persistent variables

Open
#34 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
frontend

Research direction

The issue names no files, tests, or entry points. Start by locating the reload handling and the UI that displays the lambda-calculus execution context; determine how predefined variables should be presented and persisted across sessions, then define completion criteria for both behaviors.

Written by the indexing model from the issue text.

Description

enhancement

As a user, I always want to define t, f, 0, 1, 2, 3, 4, S ... a whole bunch of other things. Right now on reload, the execution context is destroyed.

this is primarily a user interface problem-- persisting the variables cross session's dead easy, it's just presenting that to the user what's defined that's the issue.

Dominant language
JavaScript
Stars
69
Forks
10
No merged PRs in 30d

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 evinism/lambda-explorer

All issues in evinism/lambda-explorer

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.