chronicles 0.0.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 2a571a9a10b54a6522d54e6071ef291e81342ea1
+  data.tar.gz: 3d7d0f17215e36e753895dfb14f5e2782d535e80
+SHA512:
+  metadata.gz: 166c6717d5c09e1b90340f6100c20a5095b61a455ac770958f4a80f246dcb35cab422a547601e1fe14caefac903d73913416fc0ee116170e0b5a867f861aed5a
+  data.tar.gz: 4557942227d44e9b9374346d06fc578b3aedd508996fecd098a5510287d16462488de92d8fa9d9e9934b0c84b328a4ed60b6a9351a19342d73f5bcebfc435154

data/.coveralls.yml

@@ -0,0 +1,2 @@
+---
+service_name: travis-ci

data/.gitignore

@@ -0,0 +1,9 @@
+*.gem
+*.lock
+.bundle/
+.yardoc/
+coverage/
+doc/
+log/
+pkg/
+tmp/

data/.metrics

@@ -0,0 +1,9 @@
+# Settings for metric_fu and its packages are collected in the `config/metrics`
+# and loaded by the Hexx::Suit::Metrics::MetricFu.
+
+begin
+  require "hexx-suit"
+  Hexx::Suit::Metrics::MetricFu.load
+rescue LoadError
+  puts "The 'hexx-suit' gem is not installed"
+end

data/.rspec

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

data/.rubocop.yml

@@ -0,0 +1,2 @@
+---
+inherit_from: "./config/metrics/rubocop.yml"

data/.travis.yml

@@ -0,0 +1,9 @@
+---
+language: ruby
+bundler_args: --without metrics
+script: rake test:coverage:run
+rvm:
+  - 2.0
+  - ruby-head
+  - rbx-2 --2.0
+  - jruby-head-20mode

data/.yardopts

@@ -0,0 +1,3 @@
+--asset LICENSE
+--exclude lib/chronicles/version.rb
+--output doc/api

data/Gemfile

@@ -0,0 +1,5 @@
+source "https://rubygems.org"
+
+gemspec
+
+gem "hexx-suit", "~> 2.2", group: :metrics if RUBY_ENGINE == "ruby"

data/Guardfile

@@ -0,0 +1,15 @@
+# encoding: utf-8
+
+guard :rspec, cmd: "bundle exec rspec" do
+
+  watch(%r{^lib/(.+)\.rb$}) do |m|
+    "spec/tests/#{ m[1] }_spec.rb"
+  end
+
+  watch(%r{spec/tests/.+_spec\.rb})
+
+  watch("lib/chronicles.rb")   { "spec" }
+  watch("spec/spec_helper.rb") { "spec" }
+  watch(%r{spec/support/})     { "spec" }
+
+end # guard :rspec

data/LICENSE

@@ -0,0 +1,21 @@
+The MIT License
+
+Copyright (c) 2015 Andrew Kozin (nepalez), andrew.kozin@gmail.com
+
+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,198 @@
+Chronicles
+===================
+
+[![Gem Version](https://img.shields.io/gem/v/chronicles.svg?style=flat)][gem]
+[![Build Status](https://img.shields.io/travis/nepalez/chronicles/master.svg?style=flat)][travis]
+[![Dependency Status](https://img.shields.io/gemnasium/nepalez/chronicles.svg?style=flat)][gemnasium]
+[![Code Climate](https://img.shields.io/codeclimate/github/nepalez/chronicles.svg?style=flat)][codeclimate]
+[![Coverage](https://img.shields.io/coveralls/nepalez/chronicles.svg?style=flat)][coveralls]
+[![Inline docs](http://inch-ci.org/github/nepalez/chronicles.svg)][inch]
+
+[codeclimate]: https://codeclimate.com/github/nepalez/chronicles
+[coveralls]: https://coveralls.io/r/nepalez/chronicles
+[gem]: https://rubygems.org/gems/chronicles
+[gemnasium]: https://gemnasium.com/nepalez/chronicles
+[travis]: https://travis-ci.org/nepalez/chronicles
+[inch]: https://inch-ci.org/github/nepalez/chronicles
+
+Allow remembering object methods' calls.
+
+Installation
+------------
+
+Add this line to your application's Gemfile:
+
+```ruby
+# Gemfile
+gem "chronicles"
+```
+
+Then execute:
+
+```
+bundle
+```
+
+Or add it manually:
+
+```
+gem install chronicles
+```
+
+Usage
+-----
+
+```ruby
+class Test
+  include Chronicles
+
+  def initialize
+    start_chronicles
+    # ...
+  end
+
+  public    attr_reader :foo
+  protected attr_reader :bar
+  private   attr_reader :baz
+end
+
+test = Test.new
+test.chronicles # => []
+
+test.foo
+test.chronicles # => [:foo]
+
+test.send :bar
+test.chronicles # => [:foo, :bar]
+
+test.send :baz
+test.chronicles # => [:foo, :bar, :baz]
+
+test.foo
+test.chronicles # => [:foo, :bar, :baz, :foo]
+
+test.chronicles.clear
+test.chronicles # => []
+```
+
+You can restrict chronicles by public, private or protected methods only:
+
+```ruby
+class Test
+  # ...
+  def initialize
+    start_chronicles private: false
+  end
+end
+
+test.foo       # public
+test.send :bar # protected
+test.send :baz # private
+test.chronicles # => [:foo, :bar]
+```
+
+You can explicitly set methods to look for:
+
+```ruby
+class Test
+  # ...
+  def initialize
+    start_chronicles only: [:bar]
+  end
+end
+
+test.foo       # public
+test.send :bar # protected
+test.send :baz # private
+test.chronicles # => [:bar]
+```
+
+Or exclude them from being registered:
+
+```ruby
+class Test
+  # ...
+  def initialize
+    start_chronicles except: [:bar]
+  end
+end
+
+test.foo       # public
+test.send :bar # protected
+test.send :baz # private
+test.chronicles # => [:foo, :baz]
+```
+
+Or combine those conditions:
+
+```ruby
+class Test
+  # ...
+  def initialize
+    start_chronicles protected: false, except: [:foo]
+  end
+end
+
+test.foo       # public
+test.send :bar # protected
+test.send :baz # private
+test.chronicles # => [:baz]
+```
+
+Actually, you can start chronicles after initialization and do it several times to add new methods to be looked for.
+
+The problem is all methods included to the chronicle will be kept registered. To stop registering selected methods use the `stop_chronicles`:
+
+```ruby
+test.chronicles  # => []
+
+test.start_chronicles only: [:foo, :bar]
+test.foo
+test.bar
+test.baz
+test.chronicles  # => [:foo, :bar]
+
+test.start_chronicles only: :baz
+test.foo
+test.bar
+test.baz
+test.chronicles # => [:foo, :bar, :foo, :bar, :baz]
+
+test.stop_chronicles except: :baz
+test.foo
+test.bar
+test.baz
+test.chronicles # => [:foo, :bar, :foo, :bar, :baz, :baz]
+```
+
+Compatibility
+-------------
+
+Tested under rubies compatible to API 2.0+:
+
+* MRI 2.0+
+* Rubinius (mode 2.0+)
+* JRuby 9.0.0.0 (mode 2.0+)
+
+Uses [RSpec] 3.0+ for testing and [hexx-suit] for dev/test tools collection.
+
+[RSpec]: http://rspec.info/
+[hexx-suit]: http://github.com/nepalez/hexx-suit
+
+Contributing
+------------
+
+* Fork the project.
+* Read the [STYLEGUIDE](config/metrics/STYLEGUIDE).
+* Make your feature addition or bug fix.
+* Add tests for it. This is important so I don't break it in a
+  future version unintentionally.
+* Commit, do not mess with Rakefile or version
+  (if you want to have your own version, that is fine but bump version
+  in a commit by itself I can ignore when I pull)
+* Send me a pull request. Bonus points for topic branches.
+
+License
+-------
+
+See the [MIT LICENSE](LICENSE).

data/Rakefile

@@ -0,0 +1,22 @@
+# encoding: utf-8
+begin
+  require "bundler/setup"
+rescue LoadError
+  puts "You must `gem install bundler` and `bundle install` to run rake tasks"
+  exit
+end
+
+# Loads bundler tasks
+Bundler::GemHelper.install_tasks
+
+# Loads the Hexx::RSpec and its tasks
+begin
+  require "hexx-suit"
+  Hexx::Suit.install_tasks
+rescue LoadError
+  require "hexx-rspec"
+  Hexx::RSpec.install_tasks
+end
+
+# Sets the Hexx::RSpec :test task to default
+task default: "test:coverage:run"

data/chronicles.gemspec

@@ -0,0 +1,22 @@
+$:.push File.expand_path("../lib", __FILE__)
+require "chronicles/version"
+
+Gem::Specification.new do |gem|
+
+  gem.name        = "chronicles"
+  gem.version     = Chronicles::VERSION.dup
+  gem.author      = "Andrew Kozin"
+  gem.email       = "andrew.kozin@gmail.com"
+  gem.homepage    = "https://github.com/nepalez/chronicles"
+  gem.summary     = "Remembering object methods' call"
+  gem.license     = "MIT"
+
+  gem.files            = `git ls-files`.split($INPUT_RECORD_SEPARATOR)
+  gem.test_files       = Dir["spec/**/*.rb"]
+  gem.extra_rdoc_files = Dir["README.md", "LICENSE"]
+  gem.require_paths    = ["lib"]
+
+  gem.required_ruby_version = "~> 2.0"
+  gem.add_development_dependency "hexx-rspec", "~> 0.4"
+
+end # Gem::Specification

data/config/metrics/STYLEGUIDE

@@ -0,0 +1,230 @@
+= Ruby Style Guide
+
+Adapted from Dan Kubb's Ruby Style Guide
+https://github.com/dkubb/styleguide/blob/master/RUBY-STYLE
+
+== Commiting:
+
+* Write descriptive commit messages, following the pattern:
+
+    [TYPE] name
+
+    The message, describing the changes being made
+
+* Use the types below to mark commits:
+
+  - FEATURE - for adding new features, or backward-compatible changes;
+  - CHANGE - for backward-incompatible changes;
+  - BUG FIX - for fixing bugs;
+  - REFACTORING - for other changes of the code not affecting the API;
+  - OTHER - for changes in documentaton, metrics etc, not touching the code;
+  - VERSION - for version changes.
+
+* Always separate commits of different types (such as FEATURE and CHANGE).
+
+* Try to separate various features from each other.
+
+* Include specification to the same commit as the code.
+
+* Run all tests before making a commit.
+  Never commit the code that break unit tests.
+
+* Use metric (run `rake check`) before making a commit.
+
+* Do refactoring before making a commit. Best writing is rewriting.
+
+* Follow semantic versioning.
+
+    http://semver.org/
+
+* For versions name the commit after a version number, following the pattern:
+
+    VERSION 1.0.0-rc2
+
+
+== Formatting:
+
+* Use UTF-8. Declare encoding in the first line of every file.
+
+    # encoding: utf-8
+
+* Use 2 space indent, no tabs.
+
+* Use Unix-style line endings.
+
+* Use spaces around operators, after commas, colons and semicolons,
+  around { and before }.
+
+* No spaces after (, [ and before ], ).
+
+* Align `when` and `else` with `case`.
+
+* Use an empty line before the return value of a method (unless it
+  only has one line), and an empty line between defs.
+
+* Use empty lines to break up a long method into logical paragraphs.
+
+* Keep lines fewer than 80 characters.
+
+* Strip trailing whitespace.
+
+
+== Syntax:
+
+* Write for 2.0.
+
+* Use double quotes
+  
+    http://viget.com/extend/just-use-double-quoted-ruby-strings
+
+* Use def with parentheses when there are arguments.
+
+* Never use for, unless you exactly know why.
+
+* Never use then, except in case statements.
+
+* Use when x then ... for one-line cases.
+
+* Use &&/|| for boolean expressions, and/or for control flow. (Rule
+  of thumb: If you have to use outer parentheses, you are using the
+  wrong operators.)
+
+* Avoid double negation (!!), unless Null Objects are expected.
+  
+    http://devblog.avdi.org/2011/05/30/null-objects-and-falsiness
+
+* Avoid multiline ?:, use if.
+
+* Use {...} when defining blocks on one line. Use do...end for multiline
+  blocks.
+
+* Avoid return where not required.
+
+* Use ||= freely.
+
+* Use OO regexps, and avoid =~ $0-9, $~, $` and $' when possible.
+
+* Do not use Enumerable#inject when the "memo" object does not change between
+  iterations, use Enumerable#each_with_object instead (in ruby 1.9,
+  active_support and backports).
+
+* Prefer ENV.fetch to ENV[] syntax.
+  Prefer block syntax for ENV.fetch to usage of the second argument.
+
+
+== Naming:
+
+* Use snake_case for methods.
+
+* Use CamelCase for classes and modules. (Keep acronyms like HTTP,
+  RFC, XML uppercase.)
+
+* Use SCREAMING_SNAKE_CASE for other constants.
+
+* Do not use single letter variable names. Avoid uncommunicative names.
+
+* Use consistent variable names. Try to keep the variable names close
+  to the object class name.
+
+* Use names prefixed with _ for unused variables.
+
+* When defining a predicate method that compares against another object of
+  a similar type, name the argument "other".
+
+* Prefer map over collect, detect over find, select over find_all.
+
+* Use def self.method to define singleton methods.
+
+* Avoid alias when alias_method will do.
+
+
+== Comments:
+
+* Use YARD and its conventions for API documentation. Don't put an
+  empty line between the comment block and the def.
+
+* Comments longer than a word are capitalized and use punctuation.
+  Use one space after periods.
+
+* Avoid superfluous comments.
+
+
+== Code structuring:
+
+* Break code into packages, decoupled from the environment.
+
+* Wrap packages into gems.
+
+* Inject dependencies explicitly.
+  Leave all outer references on the border of any package. Inside
+  the package use internal references only.
+
+* Follow SOLID principles.
+
+    http://en.wikipedia.org/wiki/SOLID_(object-oriented_design)
+
+* Only give a method one purpose for existing. If you pass in a boolean
+  to a method, what you're saying is that this method has two different
+  behaviours. Just split it into two single purpose methods. If you have
+  to use the words "AND" or "OR" to describe what the method does it
+  probably does too much.
+
+* Avoid long methods.
+  Try to keep them at no more than 6 lines long, and preferably 4 or less.
+
+  If sections of a method are logically separate by blank lines, then
+  that's probably a sign that those sections should be split into separate
+  methods.
+
+* Avoid hashes-as-optional-parameters. Does the method do too much?
+
+* Avoid long parameter lists.
+
+* Add "global" methods to Kernel (if you have to) and make them private.
+
+* Use OptionParser for parsing complex command line options and
+  ruby -s for trivial command line options.
+
+* Avoid needless metaprogramming.
+
+* Always freeze objects assigned to constants.
+
+
+== General:
+
+* Code in a functional way, avoid mutation when it makes sense.
+
+* Try to have methods either return the state of the object and have
+  no side effects, or return self and have side effects. This is
+  otherwise known as Command-query separation (CQS):
+
+    http://en.wikipedia.org/wiki/Command-query_separation
+
+* Do not mutate arguments unless that is the purpose of the method.
+
+* Try following TRUE heuristics by Sandi Metz
+
+    http://designisrefactoring.com/2015/02/08/introducing-sandi-metz-true/
+
+* Do not mess around in core classes when writing libraries.
+  Namespace your code inside the modules, or wrap core classes to
+  decorators of your own.
+
+* Do not program defensively.
+  
+    http://www.erlang.se/doc/programming_rules.shtml#HDR11
+
+* Keep the code simple.
+
+* Don't overdesign.
+
+* Don't underdesign.
+
+* Avoid bugs.
+
+* Read other style guides and apply the parts that don't dissent with
+  this list.
+
+* Be consistent.
+
+* Use common sense.