Nodeclipse/coffeescript-eclipse

Issues

• Unable to open java classes

  #29 opened 10 years ago by damiencuvillier
  1

• basic CSON support (CoffeeScript Object Notation)

  #28 opened 10 years ago by MetaMemoryT
  0

• Improve completion with tern?

  #27 opened 10 years ago by angelozerr
  2

• ' "XtextReconcilerJob" has encountered a problem' in 4.3.1 onwards

  #19 opened 11 years ago by mgomez-dgt
  46

• Syntax errors break XtextReconciler and outline

  #25 opened 11 years ago by jthomaskerr
  1

• Cooperate with the transpiler plugin

  #26 opened 11 years ago by gossi
  2

• CSEP on Luna

  #24 opened 11 years ago by paulvi
  1

• allow other indentation than tabs (e.g two spaces)

  #13 opened 11 years ago by scharf
  5

• fix the custom lexer to be able to handle the whitespace at the end of the file

  #21 opened 11 years ago by paulvi
  3

• XtextDocument and XtextResource have run out of sync // in 4.3.1 JEE

  #20 opened 11 years ago by dangelion
  3

• False syntax error on a.b.c = "x"

  #18 opened 11 years ago by agronholm
  5

• [feature request] Show JavaScript preview for edited coffee file

  #14 opened 11 years ago by paulvi
  1

• build error on Maven3

  #17 opened 11 years ago by tomotaro1065
  2

• Setup CI

  #16 opened 11 years ago by paulvi
  0

• [Task] make maintenance 0.3 release

  #1 opened 11 years ago by paulvi
  16

• Refactor namespace to org.nodeclipse.coffeescript

  #8 opened 12 years ago by paulvi
  2

• Can't install 0.2.2 inside Eclipse Kepler for Java/DSL developers

  #15 opened 11 years ago by paulvi
  1

• Build is not explicit / slow

  #9 opened 11 years ago by paulvi
  10

• Upgrade to Xtext 2.4

  #2 opened 12 years ago by paulvi
  5

• Add maven / tycho support (cse)

  #3 opened 11 years ago by paulvi
  1

• Migrate to new p2 repository

  #4 opened 11 years ago by pulse00
  11

• x={'foo':7} is parsed incorrectly

  #10 opened 11 years ago by scharf
  3

• /"/ and /'/ are not parsed correctly

  #11 opened 11 years ago by scharf
  1

• strings are parsed incorrectly when an unexpected character after a \ is used

  #12 opened 11 years ago by scharf
  0