jets 1.9.7 → 1.9.8

data/vendor/rails/actionpack/lib/action_dispatch/routing/routes_proxy.rb

@@ -1,69 +0,0 @@
-# frozen_string_literal: true
-
-require "active_support/core_ext/array/extract_options"
-
-module ActionDispatch
-  module Routing
-    class RoutesProxy #:nodoc:
-      include ActionDispatch::Routing::UrlFor
-
-      attr_accessor :scope, :routes
-      alias :_routes :routes
-
-      def initialize(routes, scope, helpers, script_namer = nil)
-        @routes, @scope = routes, scope
-        @helpers = helpers
-        @script_namer = script_namer
-      end
-
-      def url_options
-        scope.send(:_with_routes, routes) do
-          scope.url_options
-        end
-      end
-
-    private
-      def respond_to_missing?(method, _)
-        super || @helpers.respond_to?(method)
-      end
-
-      def method_missing(method, *args)
-        if @helpers.respond_to?(method)
-          self.class.class_eval <<-RUBY, __FILE__, __LINE__ + 1
-            def #{method}(*args)
-              options = args.extract_options!
-              options = url_options.merge((options || {}).symbolize_keys)
-
-              if @script_namer
-                options[:script_name] = merge_script_names(
-                  options[:script_name],
-                  @script_namer.call(options)
-                )
-              end
-
-              args << options
-              @helpers.#{method}(*args)
-            end
-          RUBY
-          public_send(method, *args)
-        else
-          super
-        end
-      end
-
-      # Keeps the part of the script name provided by the global
-      # context via ENV["SCRIPT_NAME"], which `mount` doesn't know
-      # about since it depends on the specific request, but use our
-      # script name resolver for the mount point dependent part.
-      def merge_script_names(previous_script_name, new_script_name)
-        return new_script_name unless previous_script_name
-
-        resolved_parts = new_script_name.count("/")
-        previous_parts = previous_script_name.count("/")
-        context_parts = previous_parts - resolved_parts + 1
-
-        (previous_script_name.split("/").slice(0, context_parts).join("/")) + new_script_name
-      end
-    end
-  end
-end

data/vendor/rails/actionpack/lib/action_dispatch/routing/url_for.rb

@@ -1,236 +0,0 @@
-# frozen_string_literal: true
-
-module ActionDispatch
-  module Routing
-    # In <tt>config/routes.rb</tt> you define URL-to-controller mappings, but the reverse
-    # is also possible: a URL can be generated from one of your routing definitions.
-    # URL generation functionality is centralized in this module.
-    #
-    # See ActionDispatch::Routing for general information about routing and routes.rb.
-    #
-    # <b>Tip:</b> If you need to generate URLs from your models or some other place,
-    # then ActionController::UrlFor is what you're looking for. Read on for
-    # an introduction. In general, this module should not be included on its own,
-    # as it is usually included by url_helpers (as in Rails.application.routes.url_helpers).
-    #
-    # == URL generation from parameters
-    #
-    # As you may know, some functions, such as ActionController::Base#url_for
-    # and ActionView::Helpers::UrlHelper#link_to, can generate URLs given a set
-    # of parameters. For example, you've probably had the chance to write code
-    # like this in one of your views:
-    #
-    #   <%= link_to('Click here', controller: 'users',
-    #           action: 'new', message: 'Welcome!') %>
-    #   # => <a href="/users/new?message=Welcome%21">Click here</a>
-    #
-    # link_to, and all other functions that require URL generation functionality,
-    # actually use ActionController::UrlFor under the hood. And in particular,
-    # they use the ActionController::UrlFor#url_for method. One can generate
-    # the same path as the above example by using the following code:
-    #
-    #   include UrlFor
-    #   url_for(controller: 'users',
-    #           action: 'new',
-    #           message: 'Welcome!',
-    #           only_path: true)
-    #   # => "/users/new?message=Welcome%21"
-    #
-    # Notice the <tt>only_path: true</tt> part. This is because UrlFor has no
-    # information about the website hostname that your Rails app is serving. So if you
-    # want to include the hostname as well, then you must also pass the <tt>:host</tt>
-    # argument:
-    #
-    #   include UrlFor
-    #   url_for(controller: 'users',
-    #           action: 'new',
-    #           message: 'Welcome!',
-    #           host: 'www.example.com')
-    #   # => "http://www.example.com/users/new?message=Welcome%21"
-    #
-    # By default, all controllers and views have access to a special version of url_for,
-    # that already knows what the current hostname is. So if you use url_for in your
-    # controllers or your views, then you don't need to explicitly pass the <tt>:host</tt>
-    # argument.
-    #
-    # For convenience reasons, mailers provide a shortcut for ActionController::UrlFor#url_for.
-    # So within mailers, you only have to type +url_for+ instead of 'ActionController::UrlFor#url_for'
-    # in full. However, mailers don't have hostname information, and you still have to provide
-    # the +:host+ argument or set the default host that will be used in all mailers using the
-    # configuration option +config.action_mailer.default_url_options+. For more information on
-    # url_for in mailers read the ActionMailer#Base documentation.
-    #
-    #
-    # == URL generation for named routes
-    #
-    # UrlFor also allows one to access methods that have been auto-generated from
-    # named routes. For example, suppose that you have a 'users' resource in your
-    # <tt>config/routes.rb</tt>:
-    #
-    #   resources :users
-    #
-    # This generates, among other things, the method <tt>users_path</tt>. By default,
-    # this method is accessible from your controllers, views and mailers. If you need
-    # to access this auto-generated method from other places (such as a model), then
-    # you can do that by including Rails.application.routes.url_helpers in your class:
-    #
-    #   class User < ActiveRecord::Base
-    #     include Rails.application.routes.url_helpers
-    #
-    #     def base_uri
-    #       user_path(self)
-    #     end
-    #   end
-    #
-    #   User.find(1).base_uri # => "/users/1"
-    #
-    module UrlFor
-      extend ActiveSupport::Concern
-      include PolymorphicRoutes
-
-      included do
-        unless method_defined?(:default_url_options)
-          # Including in a class uses an inheritable hash. Modules get a plain hash.
-          if respond_to?(:class_attribute)
-            class_attribute :default_url_options
-          else
-            mattr_writer :default_url_options
-          end
-
-          self.default_url_options = {}
-        end
-
-        include(*_url_for_modules) if respond_to?(:_url_for_modules)
-      end
-
-      def initialize(*)
-        @_routes = nil
-        super
-      end
-
-      # Hook overridden in controller to add request information
-      # with +default_url_options+. Application logic should not
-      # go into url_options.
-      def url_options
-        default_url_options
-      end
-
-      # Generate a URL based on the options provided, default_url_options and the
-      # routes defined in routes.rb. The following options are supported:
-      #
-      # * <tt>:only_path</tt> - If true, the relative URL is returned. Defaults to +false+.
-      # * <tt>:protocol</tt> - The protocol to connect to. Defaults to 'http'.
-      # * <tt>:host</tt> - Specifies the host the link should be targeted at.
-      #   If <tt>:only_path</tt> is false, this option must be
-      #   provided either explicitly, or via +default_url_options+.
-      # * <tt>:subdomain</tt> - Specifies the subdomain of the link, using the +tld_length+
-      #   to split the subdomain from the host.
-      #   If false, removes all subdomains from the host part of the link.
-      # * <tt>:domain</tt> - Specifies the domain of the link, using the +tld_length+
-      #   to split the domain from the host.
-      # * <tt>:tld_length</tt> - Number of labels the TLD id composed of, only used if
-      #   <tt>:subdomain</tt> or <tt>:domain</tt> are supplied. Defaults to
-      #   <tt>ActionDispatch::Http::URL.tld_length</tt>, which in turn defaults to 1.
-      # * <tt>:port</tt> - Optionally specify the port to connect to.
-      # * <tt>:anchor</tt> - An anchor name to be appended to the path.
-      # * <tt>:trailing_slash</tt> - If true, adds a trailing slash, as in "/archive/2009/"
-      # * <tt>:script_name</tt> - Specifies application path relative to domain root. If provided, prepends application path.
-      #
-      # Any other key (<tt>:controller</tt>, <tt>:action</tt>, etc.) given to
-      # +url_for+ is forwarded to the Routes module.
-      #
-      #    url_for controller: 'tasks', action: 'testing', host: 'somehost.org', port: '8080'
-      #    # => 'http://somehost.org:8080/tasks/testing'
-      #    url_for controller: 'tasks', action: 'testing', host: 'somehost.org', anchor: 'ok', only_path: true
-      #    # => '/tasks/testing#ok'
-      #    url_for controller: 'tasks', action: 'testing', trailing_slash: true
-      #    # => 'http://somehost.org/tasks/testing/'
-      #    url_for controller: 'tasks', action: 'testing', host: 'somehost.org', number: '33'
-      #    # => 'http://somehost.org/tasks/testing?number=33'
-      #    url_for controller: 'tasks', action: 'testing', host: 'somehost.org', script_name: "/myapp"
-      #    # => 'http://somehost.org/myapp/tasks/testing'
-      #    url_for controller: 'tasks', action: 'testing', host: 'somehost.org', script_name: "/myapp", only_path: true
-      #    # => '/myapp/tasks/testing'
-      #
-      # Missing routes keys may be filled in from the current request's parameters
-      # (e.g. +:controller+, +:action+, +:id+ and any other parameters that are
-      # placed in the path). Given that the current action has been reached
-      # through <tt>GET /users/1</tt>:
-      #
-      #   url_for(only_path: true)                        # => '/users/1'
-      #   url_for(only_path: true, action: 'edit')        # => '/users/1/edit'
-      #   url_for(only_path: true, action: 'edit', id: 2) # => '/users/2/edit'
-      #
-      # Notice that no +:id+ parameter was provided to the first +url_for+ call
-      # and the helper used the one from the route's path. Any path parameter
-      # implicitly used by +url_for+ can always be overwritten like shown on the
-      # last +url_for+ calls.
-      def url_for(options = nil)
-        full_url_for(options)
-      end
-
-      def full_url_for(options = nil) # :nodoc:
-        case options
-        when nil
-          _routes.url_for(url_options.symbolize_keys)
-        when Hash, ActionController::Parameters
-          route_name = options.delete :use_route
-          merged_url_options = options.to_h.symbolize_keys.reverse_merge!(url_options)
-          _routes.url_for(merged_url_options, route_name)
-        when String
-          options
-        when Symbol
-          HelperMethodBuilder.url.handle_string_call self, options
-        when Array
-          components = options.dup
-          polymorphic_url(components, components.extract_options!)
-        when Class
-          HelperMethodBuilder.url.handle_class_call self, options
-        else
-          HelperMethodBuilder.url.handle_model_call self, options
-        end
-      end
-
-      # Allows calling direct or regular named route.
-      #
-      #   resources :buckets
-      #
-      #   direct :recordable do |recording|
-      #     route_for(:bucket, recording.bucket)
-      #   end
-      #
-      #   direct :threadable do |threadable|
-      #     route_for(:recordable, threadable.parent)
-      #   end
-      #
-      # This maintains the context of the original caller on
-      # whether to return a path or full URL, e.g:
-      #
-      #   threadable_path(threadable)  # => "/buckets/1"
-      #   threadable_url(threadable)   # => "http://example.com/buckets/1"
-      #
-      def route_for(name, *args)
-        public_send(:"#{name}_url", *args)
-      end
-
-      protected
-
-        def optimize_routes_generation?
-          _routes.optimize_routes_generation? && default_url_options.empty?
-        end
-
-      private
-
-        def _with_routes(routes) # :doc:
-          old_routes, @_routes = @_routes, routes
-          yield
-        ensure
-          @_routes = old_routes
-        end
-
-        def _routes_context # :doc:
-          self
-        end
-    end
-  end
-end

data/vendor/rails/actionpack/lib/action_dispatch/system_test_case.rb

@@ -1,147 +0,0 @@
-# frozen_string_literal: true
-
-gem "capybara", ">= 2.15"
-
-require "capybara/dsl"
-require "capybara/minitest"
-require "action_controller"
-require "action_dispatch/system_testing/driver"
-require "action_dispatch/system_testing/browser"
-require "action_dispatch/system_testing/server"
-require "action_dispatch/system_testing/test_helpers/screenshot_helper"
-require "action_dispatch/system_testing/test_helpers/setup_and_teardown"
-require "action_dispatch/system_testing/test_helpers/undef_methods"
-
-module ActionDispatch
-  # = System Testing
-  #
-  # System tests let you test applications in the browser. Because system
-  # tests use a real browser experience, you can test all of your JavaScript
-  # easily from your test suite.
-  #
-  # To create a system test in your application, extend your test class
-  # from <tt>ApplicationSystemTestCase</tt>. System tests use Capybara as a
-  # base and allow you to configure the settings through your
-  # <tt>application_system_test_case.rb</tt> file that is generated with a new
-  # application or scaffold.
-  #
-  # Here is an example system test:
-  #
-  #   require 'application_system_test_case'
-  #
-  #   class Users::CreateTest < ApplicationSystemTestCase
-  #     test "adding a new user" do
-  #       visit users_path
-  #       click_on 'New User'
-  #
-  #       fill_in 'Name', with: 'Arya'
-  #       click_on 'Create User'
-  #
-  #       assert_text 'Arya'
-  #     end
-  #   end
-  #
-  # When generating an application or scaffold, an +application_system_test_case.rb+
-  # file will also be generated containing the base class for system testing.
-  # This is where you can change the driver, add Capybara settings, and other
-  # configuration for your system tests.
-  #
-  #   require "test_helper"
-  #
-  #   class ApplicationSystemTestCase < ActionDispatch::SystemTestCase
-  #     driven_by :selenium, using: :chrome, screen_size: [1400, 1400]
-  #   end
-  #
-  # By default, <tt>ActionDispatch::SystemTestCase</tt> is driven by the
-  # Selenium driver, with the Chrome browser, and a browser size of 1400x1400.
-  #
-  # Changing the driver configuration options is easy. Let's say you want to use
-  # the Firefox browser instead of Chrome. In your +application_system_test_case.rb+
-  # file add the following:
-  #
-  #   require "test_helper"
-  #
-  #   class ApplicationSystemTestCase < ActionDispatch::SystemTestCase
-  #     driven_by :selenium, using: :firefox
-  #   end
-  #
-  # +driven_by+ has a required argument for the driver name. The keyword
-  # arguments are +:using+ for the browser and +:screen_size+ to change the
-  # size of the browser screen. These two options are not applicable for
-  # headless drivers and will be silently ignored if passed.
-  #
-  # Headless browsers such as headless Chrome and headless Firefox are also supported.
-  # You can use these browsers by setting the +:using+ argument to +:headless_chrome+ or +:headless_firefox+.
-  #
-  # To use a headless driver, like Poltergeist, update your Gemfile to use
-  # Poltergeist instead of Selenium and then declare the driver name in the
-  # +application_system_test_case.rb+ file. In this case, you would leave out
-  # the +:using+ option because the driver is headless, but you can still use
-  # +:screen_size+ to change the size of the browser screen, also you can use
-  # +:options+ to pass options supported by the driver. Please refer to your
-  # driver documentation to learn about supported options.
-  #
-  #   require "test_helper"
-  #   require "capybara/poltergeist"
-  #
-  #   class ApplicationSystemTestCase < ActionDispatch::SystemTestCase
-  #     driven_by :poltergeist, screen_size: [1400, 1400], options:
-  #       { js_errors: true }
-  #   end
-  #
-  # Because <tt>ActionDispatch::SystemTestCase</tt> is a shim between Capybara
-  # and Rails, any driver that is supported by Capybara is supported by system
-  # tests as long as you include the required gems and files.
-  class SystemTestCase < IntegrationTest
-    include Capybara::DSL
-    include Capybara::Minitest::Assertions
-    include SystemTesting::TestHelpers::SetupAndTeardown
-    include SystemTesting::TestHelpers::ScreenshotHelper
-    include SystemTesting::TestHelpers::UndefMethods
-
-    def initialize(*) # :nodoc:
-      super
-      self.class.driver.use
-    end
-
-    def self.start_application # :nodoc:
-      Capybara.app = Rack::Builder.new do
-        map "/" do
-          run Rails.application
-        end
-      end
-
-      SystemTesting::Server.new.run
-    end
-
-    class_attribute :driver, instance_accessor: false
-
-    # System Test configuration options
-    #
-    # The default settings are Selenium, using Chrome, with a screen size
-    # of 1400x1400.
-    #
-    # Examples:
-    #
-    #   driven_by :poltergeist
-    #
-    #   driven_by :selenium, screen_size: [800, 800]
-    #
-    #   driven_by :selenium, using: :chrome
-    #
-    #   driven_by :selenium, using: :headless_chrome
-    #
-    #   driven_by :selenium, using: :firefox
-    #
-    #   driven_by :selenium, using: :headless_firefox
-    def self.driven_by(driver, using: :chrome, screen_size: [1400, 1400], options: {})
-      self.driver = SystemTesting::Driver.new(driver, using: using, screen_size: screen_size, options: options)
-    end
-
-    driven_by :selenium
-
-    ActiveSupport.run_load_hooks(:action_dispatch_system_test_case, self)
-  end
-
-  SystemTestCase.start_application
-end