Permalink
Commits on Dec 12, 2011
  1. 0.2.0

    grncdr committed Dec 12, 2011
  2. Cleanup of errors, more convenient helpers, and comments

    Errors are now located in lib/errors, and can be extended
     - They are exported as .errors
    Rendering can now also be extended more easily, the object that maps
    content-types to render functions is exported as .render
    
    Helper functions are now bound to the request context for you, so passing @data
    as a callback now works.
    grncdr committed Dec 12, 2011
  3. bin/lzrs-gen-examples

    Fix name of script in usage example
    grncdr committed Dec 12, 2011
Commits on Dec 11, 2011
  1. 0.1.4

    grncdr committed Dec 11, 2011
Commits on Dec 9, 2011
  1. 0.1.3

    grncdr committed Dec 9, 2011
  2. Oh grammar, why do you taunt me so?

    Stephen Sugden committed Dec 9, 2011
  3. 0.1.2

    grncdr committed Dec 9, 2011
  4. Add 'files' to package.json'

    grncdr committed Dec 9, 2011
  5. Updated README and examples

    grncdr committed Dec 9, 2011
  6. 0.1.1

    grncdr committed Dec 9, 2011
  7. Load examples from a JSON file

    Rather than defining examples inline, define them in a JSON file. The
    example file can be loaded by using @loadExamples with a filename. See
    ./examples/language_examples.json for the format of the file.
    
    The included script lzrs-gen-examples will load an examples file,
    perform all of the requests contained in it against a given host:port
    combination, and then re-write the file with the responses in-line.
    grncdr committed Dec 9, 2011
Commits on Dec 8, 2011
Commits on Dec 7, 2011
  1. 0.1.0

    grncdr committed Dec 7, 2011
Commits on Nov 23, 2011
  1. when handling schema requests, store in @res so custom renderers can …

    …differentiate it from regular response data
    jvinet committed Nov 23, 2011
  2. fix for non-existent routes

    jvinet committed Nov 23, 2011
  3. fixed an oh-yea-im-in-async bug

    jvinet committed Nov 23, 2011
Commits on Nov 22, 2011
  1. Revert "flatten input var arrays"

    Recent changes to the match methods mean you should consistently get
    lists where you ask for them. This means using the explode modifier in
    path parameters, and *not* using it in query string parameters
    
    This reverts commit c8e5dc2.
    grncdr committed Nov 22, 2011
  2. Clarified the constraints of URI template matching

    Added some tests and behaviour changes for the same
    grncdr committed Nov 22, 2011
  3. flatten input var arrays into comma-delimited strings so controllers …

    …can expect the same data type when used as in-URL parameters or query-string parameters
    jvinet committed Nov 22, 2011
  4. Fixes #1

    grncdr committed Nov 22, 2011
  5. Added failing test for #1

    grncdr committed Nov 22, 2011
  6. Cleaning up matchers

    Renamed `string` to `input` and tried to make some of the logic read a
    little less backwards.
    grncdr committed Nov 22, 2011