Skip to content
This repository

Sep 01, 2010

  1. Konstantin Haase

    require stringio in request_test, fixes GH #51

    authored September 01, 2010
  2. Konstantin Haase

    spec checking wether Marshal.dump(params) is possible

    authored September 01, 2010

Aug 18, 2009

  1. Adam Wiggins

    request.secure? to check for ssl encrypted connection

    Signed-off-by: Simon Rozet <simon@rozet.name>
    authored August 14, 2009 sr committed August 18, 2009

Mar 31, 2009

  1. Simon Rozet

    Use contest instead of test/spec/mini

    See <http://github.com/citrusbyte/contest> for more info. The
    contest.rb file is included under the test/ directory.
    authored March 26, 2009 rtomayko committed March 31, 2009

Jan 15, 2009

  1. Ryan Tomayko

    Fix Request#params on PUT requests [#72]

    Works around an issue introduced in Rack 0.9.0 with
    request body params not being parsed when the request method
    is PUT. This should be reverted once a fix lands in Rack.
    
    Ticket for Rack fix:
    http://rack.lighthouseapp.com/projects/22435-rack/tickets/20
    
    More:
    http://sinatra.lighthouseapp.com/projects/9779/tickets/72
    authored January 15, 2009

Jan 14, 2009

  1. Ryan Tomayko

    use Test::Unit style assertions in Sinatra specs

    authored January 14, 2009
  2. Ryan Tomayko

    Test framework refactoring

    * Adds test/helper.rb and moves mock_app and other code specific
      to testing the framework out of Sinatra::Test.
    * Do not require test/unit. The sinatra/test/unit,
      sinatra/test/spec, and sinatra/test/rspec files can be used to
      choose the framework.
    * Add Sinatra::TestHarness, which should act similar to the
      Rack::Session proposal here: http://gist.github.com/41270
    * Update the README with information on using the different test
      frameworks.
    authored January 13, 2009

Dec 21, 2008

  1. Ryan Tomayko

    I knew I shoulda taken that left turn at Hoboken

    This is a fairly large reworking of Sinatra's innards. Although
    most of the internal implementation has been modified, it
    provides the same basic feature set and is meant to be compatible
    with Sinatra 0.3.2.
    
    * The Event and EventContext classes have been removed. Sinatra
      applications are now defined within the class context of a
      Sinatra::Base subclass; each request is processed within a new
      instance.
    
    * Sinatra::Base can be used as a base class for multiple
      Rack applications within a single process and can be used as
      Rack middleware.
    
    * The routing and result type processing implementation has been
      simplified and enhanced a bit. There's a new route conditions
      system for things like :agent/:host matching and a request
      level #pass method has been added to allow an event handler to
      exit immediately, passing control to the next matching route.
    
    * Regular expressions may now be used in route patterns. Captures
      are available as an array from "params[:captures]".
    
    * The #body helper method now takes a block. The block is not
      evaluated until an attempt is made to read the body.
    
    * Options are now dynamically generated class attributes on the
      Sinatra::Base subclass (instead of OpenStruct); options are
      inherited by subclasses and may be overridden up the
      inheritance hierarchy. The Base.set manages all option related
      stuff.
    
    * The application file (app_file) detection heuristics are bit
      more sane now. This fixes some bugs with reloading and
      public/views directory detection. All thin / passenger issues
      of these type should be better now.
    
    * Error mappings are now split into to distinct layers: exception
      mappings and custom error pages. Exception mappings are registered
      with 'error(Exception)' and are run only when the app raises an
      exception. Custom error pages are registered with error(status_code)
      and are run any time the response has the status code specified.
      It's also possible to register an error page for a range of status
      codes: 'error(500..599)'.
    
    * The spec and unit testing extensions have been modified to take
      advantage of the ability to have multiple Sinatra applications.
      The Sinatra::Test module must be included within the TestCase
      in order to take advantage of these methods (unless the
      'sinatra/compat' library has been required).
    
    * Rebuilt specs from scratch for better coverage and
      organization. Sinatra 3.2 unit tests have been retained
      under ./compat to ensure a baseline level of compatibility with
      previous versions; use the 'rake compat' task to run these.
    
    A large number of existing Sinatra idioms have been deprecated but
    continue to be supported through the 'sinatra/compat' library.
    
    * The "set_option" and "set_options" methods have been deprecated
      due to redundancy; use "set".
    
    * The "env" option (Sinatra::Base.env) has been renamed to "environment"
      and deprecated because it's too easy to confuse with the request-level
      Rack environment Hash (Sinatra::Base#env).
    
    * The request level "stop" method has been renamed "halt" and
      deprecated. This is for consistency with `throw :halt`.
    
    * The request level "entity_tag" method has been renamed "etag" and
      deprecated. Both versions were previously supported.
    
    * The request level "headers" method has been deprecated. Use
      response['Header-Name'] to access and modify response headers.
    
    * Sinatra.application is deprecated. Use Sinatra::Application instead.
    
    * Setting Sinatra.application = nil to reset an application is
      deprecated. You shouldn't have to reset objects anymore.
    
    * The Sinatra.default_options Hash is deprecated. Modifying this object now
      results in "set(key, value)" invocations on the Sinatra::Base
      subclass.
    
    * The "body.to_result" convention has been deprecated.
    
    * The ServerError exception has been deprecated. Any Exception is now
      considered a ServerError.
    authored December 13, 2008
Something went wrong with that request. Please try again.