popcodeorg / popcodeorg/popcode

Syntax checking / linting for console expressions

Open
#1,265 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
JavaScript
Stars
191
Forks
143
Avg merge
4d 11h
Merged PRs (30d)
5

Description

If the coder types an expression into the console that is not syntactically valid, we should recognize that and provide good, human-readable feedback rather than sending it to the preview frame be evaluated and throw a generic syntax error.

We can probably also do some very light linting here, probably a small subset of the rules we use for linting project JavaScript code.

Very closely related to #1264

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 how console expressions are sent to the preview frame for evaluation, then read the closely related issue #1264. Done means invalid expressions receive human-readable feedback before evaluation, with an agreed small subset of project JavaScript linting rules applied where appropriate.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.