Skip to content
Permalink
Browse files

import, import.

  • Loading branch information...
apotonick committed Mar 27, 2014
0 parents commit 2b6b0568c3af9a4401da4e186e42c869c5a838cc
Showing with 116 additions and 0 deletions.
  1. +17 −0 .gitignore
  2. +4 −0 Gemfile
  3. +22 −0 LICENSE.txt
  4. +29 −0 README.md
  5. +1 −0 Rakefile
  6. +12 −0 THOUGHTS
  7. +5 −0 lib/trailblazer.rb
  8. +3 −0 lib/trailblazer/version.rb
  9. +23 −0 trailblazer.gemspec
@@ -0,0 +1,17 @@
*.gem
*.rbc
.bundle
.config
.yardoc
Gemfile.lock
InstalledFiles
_yardoc
coverage
doc/
lib/bundler/man
pkg
rdoc
spec/reports
test/tmp
test/version_tmp
tmp
@@ -0,0 +1,4 @@
source 'https://rubygems.org'

# Specify your gem's dependencies in trailblazer.gemspec
gemspec
@@ -0,0 +1,22 @@
Copyright (c) 2013 Nick Sutterer

MIT License

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.
@@ -0,0 +1,29 @@
# Trailblazer

TODO: Write a gem description

## Installation

Add this line to your application's Gemfile:

gem 'trailblazer'

And then execute:

$ bundle

Or install it yourself as:

$ gem install trailblazer

## Usage

TODO: Write usage instructions here

## Contributing

1. Fork it
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Add some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create new Pull Request
@@ -0,0 +1 @@
require "bundler/gem_tasks"
@@ -0,0 +1,12 @@
by adding new abstraction layers
* automatical think about interfaces
* testability
* more optional features, e.g. by using a representer you get HAL etc for free once included. how would that work with rabl? or easy nested forms with reform

the less associations in models the better

hi-level APIs: Invoice::Flow instead of creating I:Item out-of-sync
if your factories have 5 lines or more, your API is wrong, (Invoice::Flow)


i don't wanna show anti-patterns, i wanna show how you can make things work.
@@ -0,0 +1,5 @@
require "trailblazer/version"

module Trailblazer
# Your code goes here...
end
@@ -0,0 +1,3 @@
module Trailblazer
VERSION = "0.0.1"
end
@@ -0,0 +1,23 @@
# coding: utf-8
lib = File.expand_path('../lib', __FILE__)
$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
require 'trailblazer/version'

Gem::Specification.new do |spec|
spec.name = "trailblazer"
spec.version = Trailblazer::VERSION
spec.authors = ["Nick Sutterer"]
spec.email = ["apotonick@gmail.com"]
spec.description = %q{TODO: Write a gem description}
spec.summary = %q{TODO: Write a gem summary}
spec.homepage = ""
spec.license = "MIT"

spec.files = `git ls-files`.split($/)
spec.executables = spec.files.grep(%r{^bin/}) { |f| File.basename(f) }
spec.test_files = spec.files.grep(%r{^(test|spec|features)/})
spec.require_paths = ["lib"]

spec.add_development_dependency "bundler", "~> 1.3"
spec.add_development_dependency "rake"
end

0 comments on commit 2b6b056

Please sign in to comment.
You can’t perform that action at this time.