jashkenas/coffeescript

Support export destructured assignment

Open

#5,100 opened on Aug 26, 2018

View on GitHub
 (2 comments) (0 reactions) (0 assignees)CoffeeScript (16,577 stars) (1,980 forks)batch import
enhancementhelp wanted

Description

Choose one: is this a bug report or feature request? Feature request

@GeoffreyBooth I came across an unsupported export syntax that appears to be standard

Input Code

export {foo, bar} = item

Expected Behavior

Should transpile to export var {foo, bar} = item

Current Behavior

Doesn't compile

Possible Solution

Guessing it won't be bad to add this as a supported grammar rule

Context

Not blocking anything, just came across it while working on AST stuff

Environment

  • CoffeeScript version:
  • Node.js version:

Contributor guide

Tech stack
javascript
Domain
tooling
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.
half day
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.
clear
Prerequisites
basic CoffeeScript knowledgeunderstanding of compiler parsing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Examine the CoffeeScript grammar file (likely src/grammar.coffee) to understand how destructuring assignments and export statements are currently parsed. Look at existing export rules and how they generate JavaScript code. Implement a new grammar rule to handle `export {foo, bar} = item` and ensure it transpiles to `export var {foo, bar} = item`. Also add relevant tests.