oakmac/cuttle

handle errors from the Google Closure Compiler

Open

#4 opened on Oct 19, 2014

View on GitHub
 (1 comment) (0 reactions) (1 assignee)JavaScript (316 stars) (11 forks)batch import
enhancementhelp wanted

Description

Right now we're parsing errors that come from the ClojureScript compiler, but there are a class of errors that come from the Google Closure Compiler occasionally.

We need to handle those smartly.

Contributor guide

Tech stack
javascript
Domain
frontendtoolingdeveloper experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
JavaScriptError handling patternsGoogle Closure Compiler basicsClojureScript compiler understanding
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Examine the existing error handling code for the ClojureScript compiler in the repository (likely in the source files). Identify how errors from the Google Closure Compiler differ. Then design a parsing function that handles both compiler error outputs, possibly by checking error prefixes or formats. Look at the assignee's commits or branches for any partial work. Implement the new error handling integration, ensuring it provides useful feedback to the user.