Skip to content
Commits on Oct 15, 2012
  1. @myronmarston
  2. @myronmarston

    Change api_version to separate request_version/response_version.

    myronmarston committed
    This is important for apps that use HTTP content negotiation for 
    versioning.  The response version would be selected based on the
    Content-Type of the response (which the server might select based
    on the Accept request header).  The request version would be
    selected based on the Content-Type of the request.
    
    They need to be separately selectable, hence, separate configs.
Commits on Oct 12, 2012
  1. @myronmarston
  2. @myronmarston
  3. @myronmarston
Commits on Oct 3, 2012
  1. @myronmarston

    0.3.6 release.

    myronmarston committed
  2. @myronmarston
  3. @myronmarston

    0.3.5 release.

    myronmarston committed
  4. @myronmarston

    Fix issue with request_params_parser being used with a sinatra app th…

    myronmarston committed
    …at is instantiated multiple times.
Commits on Oct 2, 2012
  1. @myronmarston

    0.3.4 release.

    myronmarston committed
  2. @myronmarston
  3. @myronmarston

    0.3.3 release.

    myronmarston committed
  4. @myronmarston

    Fix StubApp/RequestParamsParser to play nice together.

    myronmarston committed
    There was a naming conflict on `interpol_config`, and both were
    using the sinatra app to store state.  This was problematic so
    I pulled the state-based stuff into a separate class (w/ its own
    scope) so it's no longer a problem.
  5. @myronmarston
  6. @myronmarston

    0.3.2 release.

    myronmarston committed
  7. @myronmarston

    Fix issue we ran into on staging.

    myronmarston committed
    When an error occurs and you have particular sinatra settings, it causes the routes to be re-processed, leading to a NoMethodError because it tries to do something on `params`.
    
    This fixes it by only hijacking params for the duration of the route.
Commits on Sep 26, 2012
  1. @myronmarston

    0.3.1 release.

    myronmarston committed
  2. @myronmarston

    Work around the fact that NewRelic double-processes routes.

    myronmarston committed
    It was causing the route to be re-processed with parsed params, leading to errors.
Commits on Sep 25, 2012
  1. @myronmarston
Commits on Sep 24, 2012
  1. @myronmarston

    0.3.0 release.

    myronmarston committed
  2. @myronmarston
Commits on Sep 23, 2012
  1. @myronmarston
  2. @myronmarston
  3. @myronmarston
  4. @myronmarston

    Provide a better default hash for missing params declarations.

    myronmarston committed
    These actually pass the validation by the parser.
  5. @myronmarston
  6. @myronmarston

    Make path_params/query_params proper json schema definitions.

    myronmarston committed
    Previously, they just contained the entries of a `properties` hash inside a json schema definition.
  7. @myronmarston
  8. @myronmarston
  9. @myronmarston
  10. @myronmarston

    Add RequestParamsParser.

    myronmarston committed
  11. @myronmarston

    Add DynamicStruct class.

    myronmarston committed
  12. @myronmarston

    Expose the route from an endpoint definition.

    myronmarston committed
    We need this for the request param validator.
  13. @myronmarston
Commits on Sep 21, 2012
  1. @myronmarston

    Fix endpoint definition data structures.

    myronmarston committed
    We had weird nested arrays that were confusing, since they led to loops like:
    
    endpoint.definitions.each do |definitions|
      definitions.each do |definition|
      end
    end
    
    This was due to the fact that `Endpoint#definitions` was based on the hash grouping and therefore had a nested array.  It's far less confusing to just return a flat array.  Also, in one place we were doing a linear scan based on the array rather than using the hash like we should.
Something went wrong with that request. Please try again.