You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
David Majda 6fa8ad63f9 Replace some functions with arrow functions
Because arrow functions work rather differently than normal functions (a
bad design mistake if you ask me), I decided to be conservative with the
conversion.

I converted:

  * event handlers
  * callbacks
  * arguments to Array.prototype.map & co.
  * small standalone lambda functions

I didn't convert:

  * functions assigned to object literal properties (the new shorthand
    syntax would be better here)
  * functions passed to "describe", "it", etc. in specs (because Jasmine
    relies on dynamic "this")

See #442.
8 years ago
..
api Replace some functions with arrow functions 8 years ago
behavior Replace some functions with arrow functions 8 years ago
unit Replace some functions with arrow functions 8 years ago
vendor/jasmine Upgrade jasmine and jasmine-node 11 years ago
.eslintrc.json Pass spec code through Babel before serving it to the browser 8 years ago
README.md Pass spec code through Babel before serving it to the browser 8 years ago
index.html Pass spec code through Babel before serving it to the browser 8 years ago
server Replace some functions with arrow functions 8 years ago

README.md

PEG.js Spec Suite

This is the PEG.js spec suite. It ensures PEG.js works correctly. All specs should always pass on all supported platforms.

Running in Node.js

All commands in the following steps need to be executed in PEG.js root directory (one level up from this one).

  1. Install all PEG.js dependencies, including development ones:

    $ npm install
    
  2. Execute the spec suite:

    $ make spec
    
  3. Watch the specs pass (or fail).

Running in the Browser

All commands in the following steps need to be executed in PEG.js root directory (one level up from this one).

  1. Make sure you have Node.js installed.

  2. Install all PEG.js dependencies, including development ones:

    $ npm install
    
  3. Serve the spec suite using a web server:

    $ spec/server
    
  4. Point your browser to the spec suite.

  5. Watch the specs pass (or fail).