Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Consider swapping input/output colors?

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

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
design, frontend

Research direction

Start by locating the explorer view that renders input and output history, then inspect how its colors change in dark mode. Compare the current contrast and determine a color treatment that makes inputs and outputs easy to distinguish. Done means the history is visually scannable in both regular and dark modes without mistaking outputs for inputs.

Written by the indexing model from the issue text.

Description

When using the explorer and visually scanning to look back at the history of what I wrote, I found myself consistently mistaking the outputs for the inputs. This is because the inputs are rendered in a lighter grey font, while the outputs are bright, which draws attention. This is accentuated more in dark mode.

Anyhoo, user feedback!

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.