goofy 1.0.2

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 7c1a9c1efee6bfe916d95f48592c7edadf1d059d
+  data.tar.gz: b3e2c222a1682cc93303040f33643d4acb3a7f65
+SHA512:
+  metadata.gz: 783865b05059d08ea9f1daff29d53b4f22d895b3abd94cf1312844c0570f46c06578c0fefce718974b714ba9391b177acba5f9b3b41e30f87396abbdd5c0f9cb
+  data.tar.gz: 6a718a4e276abd37c50e3ac0bc67b9fd3918165d9b033c1610ff8b97ef84c0b815e515acbbc1c985223e8843860dd6c38b157a601e35d9bb1a6abbd446784f16

data/.gems

@@ -0,0 +1,4 @@
+cutest -v 1.2.2
+rack -v 1.6.0
+tilt -v 2.0.1
+rack-test -v 0.6.3

data/.gitignore

@@ -0,0 +1,2 @@
+/pkg
+webrat.log

data/CHANGELOG

@@ -0,0 +1,47 @@
+3.5.0
+
+* Add `not_found` hook for customizing the 404 error.
+
+* Remove undocumented `header` matcher.
+
+* Depend explicitly on Rack 1.6.x.
+
+* Experimental feature: `param` now accepts a second parameter
+  with a default value.
+
+3.4.0
+
+* Add `Goofy::Safe` plugin. This plugin contains security related
+  defaults.
+
+3.3.0
+
+* Restrict when to add the default content type.
+
+3.2.0
+
+* Return 404 when status is not explicitly set and body is empty.
+
+3.1.1
+
+* Add support for custom default layouts.
+
+3.1.0
+
+* Do a deep clone of the settings object during inheritance.
+* Start namespacing plugins (i.e. settings[:render]).
+* Use rack/test when doing `require 'Goofy/test'`.
+* Capybara available via `require 'Goofy/capybara'`.
+* Use a default hash for the render plugin.
+* Allow the use of custom Request and Response objects.
+
+3.0.0
+
+* Remove Goofy.build. Use subclassing instead.
+* Remove warnings.
+* Use Goofy::Response instead of Rack::Response.
+* Integrate Goofy.plugin and Goofy.settings.
+* Remove Goofy::VERSION.
+* Rename _call to call! (inspired from Sinatra).
+* Fix a memory leak with the caching used in Tilt.
+* Adding syntax highlighting to the README Code blocks

data/CONTRIBUTING

@@ -0,0 +1,19 @@
+This code tries to solve a particular problem with a very simple
+implementation. We try to keep the code to a minimum while making
+it as clear as possible. The design is very likely finished, and
+if some feature is missing it is possible that it was left out on
+purpose. That said, new usage patterns may arise, and when that
+happens we are ready to adapt if necessary.
+
+A good first step for contributing is to meet us on IRC and discuss
+ideas. We spend a lot of time on #lesscode at freenode, always ready
+to talk about code and simplicity. If connecting to IRC is not an
+option, you can create an issue explaining the proposed change and
+a use case. We pay a lot of attention to use cases, because our
+goal is to keep the code base simple. Usually the result of a
+conversation is the creation of a different tool.
+
+Please don't start the conversation with a pull request. The code
+should come at last, and even though it may help to convey an idea,
+more often than not it draws the attention to a particular
+implementation.

data/Gemfile

@@ -0,0 +1,4 @@
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in goofy.gemspec
+gemspec

data/LICENSE

@@ -0,0 +1,23 @@
+Copyright (c) 2008-2009 Christian Neukirchen
+Copyright (c) 2010-2015 Michel Martens
+Copyright (c) 2010-2015 Damian Janowski
+Copyright (c) 2010-2015 Cyril David
+Copyright (c) 2013-2015 Francesco Rodríguez
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,67 @@
+# Goofy
+
+A microframework for web development heavily based on [Cuba](http://cuba.is)
+
+![Goofy](http://www.coloring-book.info/coloring/Goofy/goofy_12.jpg)
+
+## Description
+
+Goofy is a microframework for web heavily based on [Cuba](http://cuba.is).
+Cuba is the fastest ruby microframework at the moment.
+Goofy is fast as [Cuba](http://cuba.is) but more featured and structured.
+
+## Installation
+
+    $ gem install goofy
+
+## Usage
+
+Run:
+
+    $ goofy help
+
+To get nessecary information.
+
+## Controllers
+
+Goofy controllers follow SRP(Single Responsibility Principle), in other words each action maps to one controller.
+Goofy controllers use [Prong](https://github.com/EhsanYousefi/Prong) in order to support rails-like callbacks.
+Every method that available in Cuba router is available in Goofy controller like `res.write`.
+Create new Goofy application and generate a controller to get to know Goofy controllers.
+
+Services
+--------
+In order to understand Goofy services, take a look at [Wisper](https://github.com/krisleech/wisper) documentation, in other words Goofy uses [Wisper](https://github.com/krisleech/wisper) to decouple core business logic from external concerns in Hexagonal style architectures.
+
+## Router
+
+There is no difference between Goofy router and Cuba router expect controller method:
+```ruby
+# app/controlers/welcome_controller.rb
+class WelcomeController < ApplicationController
+  def response
+    res.write "Foo Bar"
+  end
+end
+```
+```ruby
+# config/router.rb
+Goofy.define do
+  on get, "welcome" do
+    controller WelcomeController
+  end
+end
+```
+
+## Test
+
+Goofy uses [Rspec](https://github.com/rspec/rspec) as default test system.
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/EhsanYousefi/closet. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](contributor-covenant.org) code of conduct.
+
+
+## License
+
+The gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).

data/app/.rspec

@@ -0,0 +1,2 @@
+--color
+--require spec_helper

data/app/Gemfile

@@ -0,0 +1,13 @@
+source 'https://rubygems.org'
+
+# Microframework for web applications
+gem 'goofy', '~> 1.0.0', :require => ['goofy','goofy/controller']
+# A micro library providing Ruby objects with Publish-Subscribe capabilities
+gem 'wisper'
+# A wonderfully simple way to load your code
+gem 'require_all'
+
+group :test, :development do
+  # Behaviour Driven Development for Ruby
+  gem 'rspec'
+end

data/app/app/controllers/application_controller.rb

@@ -0,0 +1,3 @@
+class ApplicationController < Goofy::Controller
+  
+end

data/app/config.ru

@@ -0,0 +1,4 @@
+# This file is used by Rack-based servers to start the application.
+
+require ::File.expand_path('../config/environment', __FILE__)
+run Goofy

data/app/config/environment.rb

@@ -0,0 +1,9 @@
+require 'rubygems'
+require 'bundler'
+Bundler.require(:default, ENV["RACK_ENV"])
+require "require_all"
+require "goofy"
+require "goofy/controller"
+require_all './config/initializers'
+require_all './app'
+require_relative "routes"

data/app/config/routes.rb

@@ -0,0 +1,7 @@
+Goofy.define do
+
+  # on get, "welcome" do
+  #   controller WelcomeController
+  # end
+
+end

data/app/spec/helpers.rb

@@ -0,0 +1,2 @@
+module Helpers
+end

data/app/spec/helpers/goofy.rb

@@ -0,0 +1,11 @@
+module Helpers::Goofy
+  
+  def app
+    Goofy
+  end
+
+  def response
+    self.last_response
+  end
+
+end

data/app/spec/spec_helper.rb

@@ -0,0 +1,107 @@
+require 'require_all'
+require ::File.expand_path('../../config/environment', __FILE__)
+require 'rack/test'
+# require helpers
+require "helpers"
+require_all './spec/helpers'
+
+# This file was generated by the `rspec --init` command. Conventionally, all
+# specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.
+# The generated `.rspec` file contains `--require spec_helper` which will cause
+# this file to always be loaded, without a need to explicitly require it in any
+# files.
+#
+# Given that it is always loaded, you are encouraged to keep this file as
+# light-weight as possible. Requiring heavyweight dependencies from this file
+# will add to the boot time of your test suite on EVERY test run, even for an
+# individual file that may not need all of that loaded. Instead, consider making
+# a separate helper file that requires the additional dependencies and performs
+# the additional setup, and require it from the spec files that actually need
+# it.
+#
+# The `.rspec` file also contains a few flags that are not defaults but that
+# users commonly want.
+#
+# See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration
+RSpec.configure do |config|
+  # include rack helper methods
+  config.include Rack::Test::Methods
+  # include goofy helper
+  config.include Helpers::Goofy
+  # rspec-expectations config goes here. You can use an alternate
+  # assertion/expectation library such as wrong or the stdlib/minitest
+  # assertions if you prefer.
+  config.expect_with :rspec do |expectations|
+    # This option will default to `true` in RSpec 4. It makes the `description`
+    # and `failure_message` of custom matchers include text for helper methods
+    # defined using `chain`, e.g.:
+    #     be_bigger_than(2).and_smaller_than(4).description
+    #     # => "be bigger than 2 and smaller than 4"
+    # ...rather than:
+    #     # => "be bigger than 2"
+    expectations.include_chain_clauses_in_custom_matcher_descriptions = true
+  end
+
+  # rspec-mocks config goes here. You can use an alternate test double
+  # library (such as bogus or mocha) by changing the `mock_with` option here.
+  config.mock_with :rspec do |mocks|
+    # Prevents you from mocking or stubbing a method that does not exist on
+    # a real object. This is generally recommended, and will default to
+    # `true` in RSpec 4.
+    mocks.verify_partial_doubles = true
+  end
+
+# The settings below are suggested to provide a good initial experience
+# with RSpec, but feel free to customize to your heart's content.
+=begin
+  # These two settings work together to allow you to limit a spec run
+  # to individual examples or groups you care about by tagging them with
+  # `:focus` metadata. When nothing is tagged with `:focus`, all examples
+  # get run.
+  config.filter_run :focus
+  config.run_all_when_everything_filtered = true
+
+  # Allows RSpec to persist some state between runs in order to support
+  # the `--only-failures` and `--next-failure` CLI options. We recommend
+  # you configure your source control system to ignore this file.
+  config.example_status_persistence_file_path = "spec/examples.txt"
+
+  # Limits the available syntax to the non-monkey patched syntax that is
+  # recommended. For more details, see:
+  #   - http://rspec.info/blog/2012/06/rspecs-new-expectation-syntax/
+  #   - http://www.teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/
+  #   - http://rspec.info/blog/2014/05/notable-changes-in-rspec-3/#zero-monkey-patching-mode
+  config.disable_monkey_patching!
+
+  # This setting enables warnings. It's recommended, but in some cases may
+  # be too noisy due to issues in dependencies.
+  config.warnings = true
+
+  # Many RSpec users commonly either run the entire suite or an individual
+  # file, and it's useful to allow more verbose output when running an
+  # individual spec file.
+  if config.files_to_run.one?
+    # Use the documentation formatter for detailed output,
+    # unless a formatter has already been configured
+    # (e.g. via a command-line flag).
+    config.default_formatter = 'doc'
+  end
+
+  # Print the 10 slowest examples and example groups at the
+  # end of the spec run, to help surface which specs are running
+  # particularly slow.
+  config.profile_examples = 10
+
+  # Run specs in random order to surface order dependencies. If you find an
+  # order dependency and want to debug it, you can fix the order by providing
+  # the seed, which is printed after each run.
+  #     --seed 1234
+  config.order = :random
+
+  # Seed global randomization in this process using the `--seed` CLI option.
+  # Setting this allows you to use `--seed` to deterministically reproduce
+  # test failures related to randomization by passing the same `--seed` value
+  # as the one that triggered the failure.
+  Kernel.srand config.seed
+=end
+end

data/benchmark/measure.rb

@@ -0,0 +1,35 @@
+require "benchmark"
+require "../lib/goofy"
+require "../lib/goofy/controller"
+
+class HomeController < Goofy::Controller
+
+  def response
+    res.write("wazzup?")
+  end
+
+end
+
+Goofy.define do
+  on "c" do
+    controller HomeController
+  end
+  on "w" do
+    res.write("wazzup?")
+  end
+end
+
+Benchmark.bmbm do |x|
+
+  x.report "with controller" do
+    10000.times do
+      Goofy.call({ "PATH_INFO" => "/c", "SCRIPT_NAME" => "/" })
+    end
+  end
+
+  x.report "without controller" do
+    10000.times do
+      Goofy.call({ "PATH_INFO" => "/w", "SCRIPT_NAME" => "/" })
+    end
+  end
+end

data/bin/check_its_goofy.rb

@@ -0,0 +1,15 @@
+class CheckItsGoofy
+  def initialize(path)
+    @path = path
+  end
+
+  def execute!
+    begin
+      file = File.read(@path + '/Gemfile')
+    rescue
+      return false
+    end
+    exsits = file.scan /goofy/
+    !exsits.empty?
+  end
+end

data/bin/goofy

@@ -0,0 +1,61 @@
+#!/usr/bin/env ruby
+require 'fileutils'
+require 'bundler'
+require_relative 'goofy_instance_creator'
+require_relative 'goofy_generator'
+require_relative 'check_its_goofy'
+
+command = ARGV[0]
+app_dir = File.dirname(__FILE__).gsub(/bin/, "app")
+current_dir = FileUtils.getwd()
+
+case command
+  when "new"
+    GoofyInstanceCreator.new(ARGV[1], app_dir, current_dir).execute!
+
+  when "console", "c"
+   if ARGV[1..-1].empty?
+     exec "racksh"
+   else
+     if ARGV[-2] == '-e' || ARGV[-2] == '--environment'
+       exec "RACK_ENV=#{ARGV.last} racksh"
+     else
+       puts "Invalid option try: goofy console -e DESIRE_ENVIRONMENT"
+     end
+   end
+
+  when "server", "s"
+    if ARGV[1..-1].empty?
+      exec "shotgun config.ru"
+    else
+      exec "shotgun #{ARGV[1..-1].join(" ")} config.ru"
+    end
+
+  when "generate", "g"
+    unless CheckItsGoofy.new(current_dir).execute!
+      puts("This is not a Goofy Application, Try this command inside root folder of a Goofy application.")
+      abort
+    end
+    GoofyGenerator::Base.new(ARGV[1], ARGV[2]).execute!
+
+  when "help"
+    puts "Usage:"
+    puts "  goofy new APP_PATH"
+    puts "Server:(shoutgun)"
+    puts "  goofy server"
+    puts "Console:(racksh)"
+    puts "  gooy console"
+    puts "Generator:"
+    puts "  Resource:"
+    puts "  goofy generate resource RESOURCE_PATH"
+    puts "  Controller:"
+    puts "  goofy generate controller CONTROLLER_PATH"
+    puts "  Service:"
+    puts "  goofy generate service SERVICE_PATH"
+    puts "  Initializer:"
+    puts "  goofy generate initializer INITIALIZER_NAME"
+    puts "-----------------------------------------------------"
+    puts "Good luck :)"
+  else
+    puts "Invalid command try: goofy help"
+end