pegjs/spec/unit/compiler/passes
David Majda f866712c90 Regularize Jasmine custom matcher signatures
The "toParse" matcher in generated-parser-behavior.spec.js effectively
had these signatures:

  toParse(input)
  toParse(input, expected)
  toParse(input, options, expected)

This commit regularizes them to:

  toParse(input)
  toParse(input, expected)
  toParse(input, expected, options)

Similarly, the "toFailToParse" matcher in
generated-parser-behavior.spec.js effectively had these signatures:

  toFailToParse(input)
  toFailToParse(input, details)
  toFailToParse(input, options, details)

This commit regularizes them to:

  toFailToParse(input)
  toFailToParse(input, details)
  toFailToParse(input, details, options)

Finally, the "toChangeAST" matcher in helpers.js effectively had these
signatures:

  toChangeAST(grammar, details)
  toChangeAST(grammar, options, details)

This commit regularizes them to:

  toChangeAST(grammar, details)
  toChangeAST(grammar, details, options)

The overall purpose of these changes is to avoid different parameters
appearing at the same position, which is hard to manage without using
"arguments".
2016-04-27 13:24:00 +02:00
..
generate-bytecode.spec.js Fix labels leaking to outer scope 2016-03-11 16:42:03 +01:00
helpers.js Regularize Jasmine custom matcher signatures 2016-04-27 13:24:00 +02:00
remove-proxy-rules.spec.js Regularize Jasmine custom matcher signatures 2016-04-27 13:24:00 +02:00
report-infinite-loops.spec.js Fix labels leaking to outer scope 2016-03-11 16:42:03 +01:00
report-left-recursion.spec.js Fix labels leaking to outer scope 2016-03-11 16:42:03 +01:00
report-missing-rules.spec.js ESLint: Set environments better 2016-01-29 14:50:38 +01:00