allow nil option

Let's parameter to be validated but still allowing it to be nil
fix showing param name in error message
Merge pull request #9 from iNecas/allow-nil

allow nil option
Merge pull request #10 from iNecas/param-in-error-message

fix showing param name in error message
reload controllers in development environment when showing apidoc

It allows instant reload of documentation content. It reloads all the
controllers only when loading the html part (not JSON), so that it's slowed
down only when refreshing the whole page and not on subsequent JSON calls.

It would be better to make this feature customizable by some setting, but for
now lets keep it stupid and simple: it's turned on only in development
environment.
Merge pull request #11 from iNecas/dev-env-reload

reload controllers in development environment when showing api doc
I dropped backbone.js, it was too heavy.
Views are now rendered in rails, its more convenient and translations can be made in future.
New DSL method - example for providing example api response.
Added new rake task (restapi:static) - one-page static documentation generator.
should fix ruby 1.9.3 error on travis
hash parameters changes (parent parameter is now included in json), validators respond to expected_type - needed for cli client
client generator added
add configuration options for reloading controllers

Two new options added to the configuration:

  * reload_controllers [true|false] - if not specified, enabled by default in development
  * api_controllers_matcher - Dir.glob like pattern for finding controllers to
    be reloaded. If not specified reloading does not work.
specs refactoring
set dummy application to reload controllers in dev env

Usefull for testing purposes.
Merge pull request #15 from iNecas/dev-env-reload

set dummy application to reload controllers in dev env
updated static page rake task
version bump
show examples not only in request details

Examples are so important that they deserve to be displayed sooner.
include examples from yml file

It's now possible to save the examples to separate yml file so that is can be
regenerated automatically and then include it in the documentation. Usefull
with combination with integration tests.

The file is loaded from `doc/restapi_examples.yml` and it might look like this:

    ---
    users#show:
    - verb: :GET
      path: /users/15
      query:
      request_data:  # parsed data sent to server
      response_data: # parsed data sent to client
      code: 404
      show_in_doc: 2 # if 0, don't include it in the documentation,
                     # it says also the order of examples in doc
      recorded: true # to distinguish between automatically generated examples
                     # and manual ones
    - verb: :GET     # there can be more examples for an action
      path: /users/14
      query: "verbose=true"
      request_data:
      response_data:
        id: 14
        name: Test User
      code: 200
      show_in_doc: 1
      recorded: true
    users#create:
    - verb: :POST
      path: /users
      query:
      request_data:
        user:
          name: Test User
      response_data:
        id: 14
        name: Test User
      code: 200
      show_in_doc: 1
      recorded: true
Merge pull request #17 from iNecas/recorded-examples

Recorded examples