mbj/unparser

Issues

• Some backslashes are dropped from heredocs

  #374 opened 6 months ago by akimd
  1

• Errors

  #196 opened 4 years ago by marcandre
  17

• Chocking on interpolation with interpolation

  #249 opened 4 years ago by akimd
  22

• Local variables whose name is a keyword

  #367 opened 7 months ago by akimd
  10

• Forward args (...)

  #363 opened 9 months ago by petekinnecom
  1

• May break on Ruby versions below `3.2.0` due to non-evaluatable `Symbol#inspect`

  #359 opened a year ago by prikha
  14

• Broken code when an op_asgn node contains a string with interpolation and the string contains a linefeed.

  #350 opened a year ago by vidarh
  4

• safe navigation operator discarded in arithmetic context

  #345 opened 2 years ago by csabahenk
  4

• unparse with comments: source_range: undefined method location

  #344 opened 2 years ago by neil-ongkingco-apollo
  5

• Symbol literals with interpolation are not allowed in hash patterns

  #340 opened 2 years ago by kddnewton
  7

• Use of mutation testing in unparser - Help needed

  #335 opened 2 years ago by belene
  1

• Block one arg comma

  #240 opened 4 years ago by pilipenok
  12

• Feature request: `unparser validate` CLI command

  #324 opened 3 years ago by dgollahon
  2

• Unparser failing to round-trip dynamic heredoc + block

  #311 opened 3 years ago by dgollahon
  1

• Invalid parser for `Sequel.~(query)`

  #280 opened 3 years ago by dgollahon
  4

• Invalid unparse for `Sequel.&(foo: 1)

  #278 opened 3 years ago by backus
  2

• Keyword arguments in Ruby 3.0

  #254 opened 4 years ago by camertron
  3

• Choking on interpolation with heredoc

  #243 opened 4 years ago by akimd
  5

• Insufficient parenthesizing

  #189 opened 4 years ago by akimd
  13

• 3.0 Syntax

  #168 opened 4 years ago by mbj
  0

• Multiple Errors

  #195 opened 4 years ago by marcandre
  3

• Handle lvars introduced from `rescue => expression` correctly.

  #203 opened 4 years ago by mbj
  0

• Error on msagn

  #194 opened 4 years ago by marcandre
  0

• Support 2.7 AST

  #129 opened 4 years ago by mbj
  9

• Unparses `foo` as `#{"foo"}`

  #82 opened 4 years ago by aekobear
  7

• Insufficient parenthesizing

  #131 opened 4 years ago by akimd
  5

• Add tests that applies all node types to all children.

  #68 opened 4 years ago by mbj
  5

• NoMethodError: undefined method `type'

  #141 opened 5 years ago by catmando
  4

• Relax parser dependency

  #138 opened 5 years ago by palkan
  7

• cannot parse then unparse this: `hash["counter"] += 1`

  #117 opened 6 years ago by catmando
  1

• I think this is a bug introduced on cleanup

  #115 opened 6 years ago by jdehaan
  5

• hash['val'] += 1 produces invald hash.[]("val") += 1

  #112 opened 6 years ago by MichaelSp
  10

• Missing emitters?

  #85 opened 6 years ago by evdubs
  7

• Unparsed code omits necessary parens

  #83 opened 6 years ago by dkubb
  6

• Provide include for choosing ruby version

  #71 opened 6 years ago by ptarjan
  2

• No emitter for node: :__LINE__ and __FILE__

  #69 opened 6 years ago by naw
  7

• Relax parser requirements to work with 2.5.0.0+

  #78 opened 7 years ago by stanhu
  3

• Unparser's approach to emitting comments is fragile

  #58 opened 9 years ago by alexdowad
  7

• Minor release from 0.2.4 to 0.2.5 dropped Ruby 2.0 support

  #65 opened 9 years ago by henrylawson
  7

• Invalid syntax emitted on until when condition has a block

  #66 opened 9 years ago by mbj
  0

• Release v1.0

  #31 opened 9 years ago by mbj
  2

• parser 2.3 is out

  #59 opened 9 years ago by troessner
  2

• Set version of RSpec as development dependency in gemspec

  #57 opened 9 years ago by alexdowad
  3

• Circular argument reference

  #47 opened 10 years ago by ravensnowbird
  1

• Can't unparse AST tree composed with AST::Sexp manually

  #39 opened 10 years ago by dredozubov
  4

• 0.0.17 Breaks 1.9.3 compatibility

  #37 opened 10 years ago by nielsm
  14

• Failure on Ruby 2.2

  #33 opened 10 years ago by mvz
  3

• Unparser adds parentheses to a + b + c

  #30 opened 10 years ago by mvidner
  9

• Fix 2.1.3 related syntax differencies

  #29 opened 10 years ago by mbj
  0

• Possible bug in unparsing of `and` and `or` operators?

  #26 opened 11 years ago by louismrose
  2