hanami 0.9.2 → 1.0.0.beta1

data/lib/hanami/generators/application/app/config/environment.rb.tt

@@ -1,4 +0,0 @@
-require 'bundler/setup'
-require 'hanami/setup'
-require_relative '../lib/<%= config[:app_name] %>'
-require_relative '../config/application'

data/lib/hanami/generators/application/app/config/routes.rb.tt

@@ -1,5 +0,0 @@
-# Configure your routes here
-# See: http://hanamirb.org/guides/routing/overview/
-#
-# Example:
-# get '/hello', to: ->(env) { [200, {}, ['Hello from Hanami!']] }

data/lib/hanami/generators/application/app/db/.gitkeep

@@ -1 +0,0 @@
-#

data/lib/hanami/generators/application/app/features_helper.rb.minitest.tt

@@ -1,11 +0,0 @@
-# Require this file for feature tests
-require_relative './spec_helper'
-
-require 'capybara'
-require 'capybara/dsl'
-
-Capybara.app = <%= config[:classified_app_name] %>::Application.new
-
-class MiniTest::Spec
-  include Capybara::DSL
-end

data/lib/hanami/generators/application/app/features_helper.rb.rspec.tt

@@ -1,12 +0,0 @@
-# Require this file for feature tests
-require_relative './spec_helper'
-
-require 'capybara'
-require 'capybara/rspec'
-
-RSpec.configure do |config|
-  config.include RSpec::FeatureExampleGroup
-
-  config.include Capybara::DSL,           feature: true
-  config.include Capybara::RSpecMatchers, feature: true
-end

data/lib/hanami/generators/application/app/gitignore.tt

@@ -1,2 +0,0 @@
-/public/assets*
-/tmp

data/lib/hanami/generators/application/app/gitignore_with_db.tt

@@ -1,4 +0,0 @@
-/db/<%= config[:app_name] %>_development
-/db/<%= config[:app_name] %>_test
-/public/assets*
-/tmp

data/lib/hanami/generators/application/app/gitignore_with_sqlite.tt

@@ -1,3 +0,0 @@
-/db/*.sqlite
-/public/assets*
-/tmp

data/lib/hanami/generators/application/app/hanamirc.tt

@@ -1,4 +0,0 @@
-<%= Hanami::Hanamirc::PROJECT_NAME %>=<%= config[:app_name] %>
-<%= Hanami::Hanamirc::ARCHITECTURE_KEY %>=<%= Hanami::Hanamirc::APP_ARCHITECTURE %>
-<%= Hanami::Hanamirc::TEST_KEY %>=<%= config[:test] %>
-<%= Hanami::Hanamirc::TEMPLATE_KEY %>=<%= config[:template] %>

data/lib/hanami/generators/application/app/lib/app_name.rb.tt

@@ -1,35 +0,0 @@
-require 'hanami/model'
-require 'hanami/mailer'
-Dir["#{ __dir__ }/<%= config[:app_name] %>/**/*.rb"].each { |file| require_relative file }
-
-Hanami::Model.configure do
-  # Database adapter
-  #
-  # Available options:
-  #
-  #  * SQL adapter
-  #    adapter :sql, 'sqlite://db/<%= config[:app_name] %>_development.sqlite3'
-  #    adapter :sql, 'postgres://localhost/<%= config[:app_name] %>_development'
-  #    adapter :sql, 'mysql://localhost/<%= config[:app_name] %>_development'
-  #
-  adapter :<%= config[:database_config][:type] %>, ENV['DATABASE_URL']
-
-  <%- if config[:database_config][:type] == :sql -%>
-  ##
-  # Migrations
-  #
-  migrations 'db/migrations'
-  schema     'db/schema.sql'
-  <%- end -%>
-end.load!
-
-Hanami::Mailer.configure do
-  root "#{ __dir__ }/<%= config[:app_name] %>/mailers"
-
-  # See http://hanamirb.org/guides/mailers/delivery
-  delivery do
-    development :test
-    test        :test
-    # production :smtp, address: ENV['SMTP_PORT'], port: 1025
-  end
-end.load!

data/lib/hanami/generators/application/app/lib/chirp/entities/.gitkeep

@@ -1 +0,0 @@
-#

data/lib/hanami/generators/application/app/lib/chirp/repositories/.gitkeep

@@ -1 +0,0 @@
-#

data/lib/hanami/generators/application/app/rspec.rspec.tt

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

data/lib/hanami/generators/application/app/spec_helper.rb.minitest.tt

@@ -1,7 +0,0 @@
-# Require this file for unit tests
-ENV['HANAMI_ENV'] ||= 'test'
-
-require_relative '../config/environment'
-require 'minitest/autorun'
-
-Hanami.boot

data/lib/hanami/generators/application/app/spec_helper.rb.rspec.tt

@@ -1,104 +0,0 @@
-# Require this file for unit tests
-ENV['HANAMI_ENV'] ||= 'test'
-
-require_relative '../config/environment'
-Hanami.boot
-
-Dir[__dir__ + '/support/**/*.rb'].each { |f| require f }
-
-# 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|
-  # 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://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax
-  #   - http://teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/
-  #   - http://myronmars.to/n/dev-blog/2014/05/notable-changes-in-rspec-3#new__config_option_to_disable_rspeccore_monkey_patching
-  config.disable_monkey_patching!
-
-  # This setting enables warnings. It's recommended, but in many cases may
-  # be too noisy due to issues in dependencies.
-  config.warnings = false
-
-  # 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/lib/hanami/generators/application/app/templates/application.html.erb.tt

@@ -1,10 +0,0 @@
-<!doctype HTML>
-<html>
-  <head>
-    <title><%= config[:classified_app_name] %></title>
-    <%%= favicon %>
-  </head>
-  <body>
-    <%%= yield %>
-  </body>
-</html>

data/lib/hanami/generators/application/app/templates/application.html.haml.tt

@@ -1,7 +0,0 @@
-!!!
-%html
-  %head
-    %title <%= config[:classified_app_name] %>
-    = favicon
-  %body
-    = yield

data/lib/hanami/generators/application/app/templates/application.html.slim.tt

@@ -1,8 +0,0 @@
-doctype html
-html
-  head
-    title
-      | <%= config[:classified_app_name] %>
-    = favicon
-  body
-    = yield

data/lib/hanami/generators/application/app/views/application_layout.rb.tt

@@ -1,7 +0,0 @@
-module <%= config[:classified_app_name] %>
-  module Views
-    class ApplicationLayout
-      include <%= config[:classified_app_name] %>::Layout
-    end
-  end
-end