|
| 1 | +<!--- |
| 2 | +Thanks for filing an issue 😄! Before you submit, please read the following: |
| 3 | +
|
| 4 | +Search open/closed issues before submitting since someone might have asked the same thing before! |
| 5 | +Our issues history stretches back to 2009, so the odds are good that your topic has come up. |
| 6 | +
|
| 7 | +If you have a support request or question please use Stack Overflow: |
| 8 | +https://stackoverflow.com/questions/tagged/coffeescript |
| 9 | +
|
| 10 | +Issues on GitHub are only related to problems of the CoffeeScript compiler itself and we cannot answer |
| 11 | +support questions here. |
| 12 | +--> |
| 13 | + |
| 14 | +Choose one: is this a bug report or feature request? |
| 15 | + |
| 16 | +<!--- |
| 17 | +Provide a general summary of the issue in the title above. |
| 18 | +
|
| 19 | +For bugs, please also preface your title with “Bug:”. For feature requests, please preface your title |
| 20 | +with “Proposal:”. Once your issue is reviewed, a maintainer will edit the title to refer to the part |
| 21 | +of the codebase most relevant to the issue (if applicable). |
| 22 | +
|
| 23 | +If your request is that CoffeeScript support a new feature recently arrived to JavaScript, please note |
| 24 | +that we generally only add features that have reached Stage 4 in the specification (in other words, |
| 25 | +the syntax is finalized and the feature is approved to be part of the next ES release). You can still |
| 26 | +open an issue, but it will likely be tagged with “[Awaiting Stage 4]” until the relevant ES feature is |
| 27 | +approved for release. See http://coffeescript.org/#contributing |
| 28 | +
|
| 29 | +There are also a handful of JavaScript features that CoffeeScript intentionally does not support. |
| 30 | +Please do not open issues regarding these. They’re listed in http://coffeescript.org/#unsupported |
| 31 | +--> |
| 32 | + |
| 33 | +### Input Code |
| 34 | +<!--- If you're describing a bug, please let us know which sample code reproduces your problem. --> |
| 35 | +<!--- If you have link from http://coffeescript.org/#try or a standalone repo please include that! --> |
| 36 | + |
| 37 | +```coffee |
| 38 | +your (code) => here |
| 39 | +``` |
| 40 | + |
| 41 | +### Expected Behavior |
| 42 | +<!--- If you’re describing a bug, tell us what should happen. --> |
| 43 | +<!--- If you’re suggesting a change/improvement, tell us how it should work. --> |
| 44 | + |
| 45 | +### Current Behavior |
| 46 | +<!--- If describing a bug, tell us what happens instead of the expected behavior. --> |
| 47 | +<!--- If suggesting a change/improvement, explain the difference from current behavior. --> |
| 48 | + |
| 49 | +### Possible Solution |
| 50 | +<!--- Not obligatory, but suggest a fix/reason for the bug, --> |
| 51 | +<!--- or ideas how to implement the addition or change. --> |
| 52 | + |
| 53 | +### Context |
| 54 | +<!--- How has this issue affected you? What are you trying to accomplish? --> |
| 55 | +<!--- Providing context helps us come up with a solution that is most useful in the real world. --> |
| 56 | + |
| 57 | +### Environment |
| 58 | +<!--- For bugs, please let us know what version of CoffeeScript you’re running: `coffee -v`. --> |
| 59 | +<!--- If you think it might be relevant, please also let us know your version of Node. --> |
| 60 | + |
| 61 | +* CoffeeScript version: |
| 62 | +* Node.js version: |
0 commit comments