event-sourcing 0.2.0.pre → 0.2.1.pre

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 1887675acd16105bd77fb6d7cf83281590a965e0352817d55c7c83a0ea56bf50
-  data.tar.gz: 00cce85ada5a577a081c18d60fc59d66bf007878b52d57b286c835f2898d7bec
+  metadata.gz: 96d248391ed71d7e3a56d1d3107a4e488d514f4c20182103148d576738927f76
+  data.tar.gz: '09e0513bf3f06d9a86b28f4bd0b4c17eccf47ca9a0534b58a30769c0618f7608'
 SHA512:
-  metadata.gz: 5279909deeb3b0f88b008180eb810a03139552de6374859b617707366a4dac3ba17380aa245a83e8e8b9b3ff6f1a7c6c383a1b66d54e36bf01f5aa2f9d96d5b6
-  data.tar.gz: 75b7e45e8479284f550d42b66bdde7e61d388fb990f55c0963d050133513fbc14d04ab10bd067ce4a11ee37181e03f3ce3f01d130da5999ddb3c221ccd39537b
+  metadata.gz: 66c4b323e9407d45255ce6426938b99e042d6317cf261ae2830e77211193f8e52dbd8644f64eac81f79711634ba10d709303d94dc2c4e2f67c2f57f9058b8c9f
+  data.tar.gz: 1f2c26f0c09b58014279426fe97f0e39833049e96208621006ed93a0d297d6dd2fb85c55baaf09caaf2204033ef2eb23180f1d3a2f67e4b6cb497ca0912ce70c

data/lib/event_sourcing/rails.rb

@@ -1,2 +1,3 @@
+require "event_sourcing"
 require "event_sourcing/rails/command_record"
 require "event_sourcing/rails/event_record"

data/lib/event_sourcing/version.rb

@@ -1,3 +1,3 @@
 module EventSourcing
-  VERSION = "0.2.0.pre"
+  VERSION = "0.2.1.pre"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: event-sourcing
 version: !ruby/object:Gem::Version
-  version: 0.2.0.pre
+  version: 0.2.1.pre
 platform: ruby
 authors:
 - The Conversation Dev Team
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-10-27 00:00:00.000000000 Z
+date: 2018-10-28 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -25,80 +25,73 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '1.16'
 - !ruby/object:Gem::Dependency
-  name: rake
+  name: pg
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '10.0'
+        version: '1.0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '10.0'
+        version: '1.0'
 - !ruby/object:Gem::Dependency
-  name: rspec
+  name: rails
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '3.0'
+        version: '5.0'
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: '6'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '3.0'
+        version: '5.0'
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: '6'
 - !ruby/object:Gem::Dependency
-  name: rails
+  name: rake
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '5'
+        version: '10.0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '5'
+        version: '10.0'
 - !ruby/object:Gem::Dependency
-  name: pg
+  name: rspec
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '1'
+        version: '3.0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '1'
-description: Event sourcing implementation for TC projects
+        version: '3.0'
+description: Simple Ruby Event Sourcing framework, with Rails support
 email: 
 executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- ".gitignore"
-- ".rspec"
-- ".ruby-gemset"
-- ".ruby-version"
-- ".travis.yml"
-- CODE_OF_CONDUCT.md
-- Gemfile
-- LICENSE.txt
-- README.md
-- Rakefile
-- bin/console
-- bin/setup
-- event-sourcing.gemspec
 - lib/event_sourcing.rb
 - lib/event_sourcing/command.rb
 - lib/event_sourcing/event.rb
@@ -107,7 +100,7 @@ files:
 - lib/event_sourcing/rails/command_record.rb
 - lib/event_sourcing/rails/event_record.rb
 - lib/event_sourcing/version.rb
-homepage: https://github.com/conversation/tc-event-sourcing
+homepage: https://github.com/conversation/event-sourcing
 licenses:
 - MIT
 metadata: {}
@@ -130,5 +123,5 @@ rubyforge_project:
 rubygems_version: 2.7.7
 signing_key: 
 specification_version: 4
-summary: TC Event sourcing library
+summary: The Conversation Event sourcing library
 test_files: []

data/.gitignore

@@ -1,15 +0,0 @@
-/.bundle/
-/.yardoc
-/_yardoc/
-/coverage/
-/doc/
-/pkg/
-/spec/reports/
-/tmp/
-Gemfile.lock
-
-# rspec failure tracking
-.rspec_status
-
-# JetBrains
-.idea/

data/.rspec

@@ -1,3 +0,0 @@
---format documentation
---color
---require spec_helper

data/.ruby-gemset

@@ -1 +0,0 @@
-tc-event-sourcing

data/.ruby-version

@@ -1 +0,0 @@
-2.5.1

data/.travis.yml

@@ -1,10 +0,0 @@
----
-addons:
-  postgresql: 9.6
-before_install: gem install bundler -v 1.17.0
-before_script: createdb -U postgres event_sourcing_test
-language: ruby
-rvm:
-- 2.4.5
-- 2.5.3
-script: bundle exec rake spec

data/CODE_OF_CONDUCT.md

@@ -1,74 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of experience,
-nationality, personal appearance, race, religion, or sexual identity and
-orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or
-advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at tiagopadrela@gmail.com. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at [http://contributor-covenant.org/version/1/4][version]
-
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/

data/Gemfile

@@ -1,6 +0,0 @@
-source "https://rubygems.org"
-
-git_source(:github) {|repo_name| "https://github.com/#{repo_name}" }
-
-# Specify your gem's dependencies in event-sourcing.gemspec
-gemspec

data/LICENSE.txt

@@ -1,21 +0,0 @@
-The MIT License (MIT)
-
-Copyright (c) 2018 The Conversation Media Group
-
-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

@@ -1,102 +0,0 @@
-# EventSourcing
-
-Simple Ruby Event Sourcing framework, with Rails support. Inspired by [Kickstarter](https://www.kickstarter.com/)'s 
-["Event Sourcing made Simple"](https://kickstarter.engineering/event-sourcing-made-simple-4a2625113224) blog post.
-
-`EventSourcing` gives you a toolset to configure and store sequences of events on any Ruby application, making it 
-possible to query an object state at any given point of time.
-
-As Martin Fowler describes the Event Sourcing concept:  
-
-> Event Sourcing ensures that all changes to application state are stored as a sequence of events. Not just can we query 
-these events, we can also use the event log to reconstruct past states, and as a foundation to automatically adjust the 
-state to cope with retroactive changes.
-> - Source: https://martinfowler.com/eaaDev/EventSourcing.html
-
-## Installation
-
-Add this line to your application's Gemfile:
-
-```ruby
-gem 'event-sourcing'
-```
-
-And then execute:
-
-    $ bundle
-
-Or install it yourself as:
-
-    $ gem install event-sourcing
-    
-## Concepts
-
-This frameworks introduces artifacts and rules to keep track of object state changes.
-
-The core artifacts of this framework are:
-
-- **Aggregates**: represent the current state of the application
-    - Usually they are persistence objects, such as "models"
-- **Events**: provide history of an aggregate, applying changes to an aggregate
-    - "Applying" an event is also known as "Calculator" on other event sourcing literature
-- **Commands**: validates and persists events
-- **Reactors**: trigger side effects as events happen
-- **Event Dispatcher**: manage which reactors will be executed after an event happens
-
-While state changing actions obey the rationale:
-
-- Aggregate state changes should be executed through a Command
-- Events are immutable, as they represent series of changes to an Aggregate
-- Reactors may be triggered after an Event occurs
-
-## Usage
-
-This framework can be used on any Ruby project, as it allows you to customize how you can handle Event persistence and
-event dispatching control flow.
-
-You can find an implementation sample at the [PORO app's README file](examples/poro_app/README.md).  
-
-## Usage with Rails
-
-You can also use this framework with Rails, as it includes an `event_sourcing/rails` module to ease up configuration.
-
-**Note:** this Rails implementation requires a database that implements serializable attributes by default,
-such as PostgreSQL JSON/Binary JSON columns.
-
-To include the Rails module, add this line to your application's Gemfile:
-
-```ruby
-gem "event-sourcing", require: "event_sourcing/rails"
-```
-
-Further installation steps and a sample implementation can be found at the [Rails' README file](examples/rails_app/README.md).
-
-## Contributing
-
-- System requirements
-    - Postgres 8.4+
-    - Ruby 2.3+
-
-After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. 
-
-You can also run `bin/console` for an interactive prompt that will allow you to experiment.
-
-Bug reports and pull requests are welcome on GitHub at https://github.com/conversation/event-sourcing.
-
-This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere
-
-to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
-
-## License
-
-The gem is available as open source under the terms of the [MIT License](LICENSE.txt).
-
-## Code of Conduct
-
-Everyone interacting in the The Conversation project’s codebases, issue trackers, chat rooms and mailing lists is
-expected to follow the [code of conduct](https://github.com/conversation/event-sourcing/blob/master/CODE_OF_CONDUCT.md).
-
-## Related Projects
-
-Thank you very much [Kickstarter](https://www.kickstarter.com/) for making the ["Event Sourcing made Simple"](https://kickstarter.engineering/event-sourcing-made-simple-4a2625113224)
-blog post. This project is heavily inspired on concepts described on it and its [Rails demo app](https://github.com/pcreux/event-sourcing-rails-todo-app-demo). 

data/Rakefile

@@ -1,6 +0,0 @@
-require "bundler/gem_tasks"
-require "rspec/core/rake_task"
-
-RSpec::Core::RakeTask.new(:spec)
-
-task :default => :spec

data/bin/console

@@ -1,14 +0,0 @@
-#!/usr/bin/env ruby
-
-require "bundler/setup"
-require "event_sourcing"
-
-# You can add fixtures and/or initialization code here to make experimenting
-# with your gem easier. You can also use a different console, if you like.
-
-# (If you use this, don't forget to add pry to your Gemfile!)
-# require "pry"
-# Pry.start
-
-require "irb"
-IRB.start(__FILE__)

data/bin/setup

@@ -1,8 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-IFS=$'\n\t'
-set -vx
-
-bundle install
-
-# Do any other automated setup that you need to do here

data/event-sourcing.gemspec

@@ -1,28 +0,0 @@
-lib = File.expand_path("../lib", __FILE__)
-$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
-
-require "event_sourcing/version"
-require "event_sourcing"
-
-Gem::Specification.new do |spec|
-  spec.name = "event-sourcing"
-  spec.version = EventSourcing::VERSION
-  spec.authors = ["The Conversation Dev Team"]
-
-  spec.summary = "TC Event sourcing library"
-  spec.description = "Event sourcing implementation for TC projects"
-  spec.homepage = "https://github.com/conversation/tc-event-sourcing"
-  spec.license = "MIT"
-
-  # Specify which files should be added to the gem when it is released.
-  # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
-  spec.files = Dir.chdir(File.expand_path('..', __FILE__)) do
-    `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features|examples)/}) }
-  end
-
-  spec.add_development_dependency "bundler", "~> 1.16"
-  spec.add_development_dependency "rake", "~> 10.0"
-  spec.add_development_dependency "rspec", "~> 3.0"
-  spec.add_development_dependency "rails", ">= 5"
-  spec.add_development_dependency "pg", ">= 1"
-end