Make a better interface for informing users of syntax errors inline

Open
#15 0 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
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
frontend

Research direction

Start by locating the code that turns the caret red when the editor detects a syntax error. Review the existing inline error behavior and any related interface entry points; done should be a decided, non-overwhelming way to inform users of syntax errors while they type.

Written by the indexing model from the issue text.

Description

enhancement

right now the caret turns red. That might be sufficient, but it's probably not a strong enough indicator.

remember: we don't want the user to get overwhelmed because they keep making syntax errors while they're typing. We want to assist them, not shout errors at them loudly.

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.