trailblazer 2.1.2 → 2.1.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 9408be91d18dd6ffcfd37798706abcd9c3ec53ec60b6b99aff17368bc2c8cba1
-  data.tar.gz: 545fbb44de7d6078941e0304c4390e28c92984a7b44cc75dc74f7c160917bffc
+  metadata.gz: 0d0ac4db20919678e762365a02e94e4882b21f933e8fec565ab277fc081a5d5b
+  data.tar.gz: d150482451d566d56d3ef1815d6d080c756001ca619769db3fe4ab914466de50
 SHA512:
-  metadata.gz: fc0cc222a82c69e04bfe3c53ee0f166a9705acb09d665a49418b9a61a1e7ae61531609d36d4444e0db386828871fdc6ee9a13ad6df215e96e3560e8d65bd3e8c
-  data.tar.gz: af02a1954582ca6c9b767d98613b51b1ca96922b988c3b6a24cd122caf7d998d8a8d60a0c945b01392432983e2cc94eb2921a6b5982796a497e72df15cc7a12a
+  metadata.gz: d48bc5c565745d3ee6293b4cc6b50c44e71618151d93e5e091a8338b8d1b38f45793b24daec644e458b71700f4cbd58f5a934813e314f4e18f843fcbc8de7676
+  data.tar.gz: f30443b34b86d148f2a9a35d60a97b593157c3f346a365664be96b7987df42d6bd29378e451000359a2eca289cd948f9a13f2c5043a82dcc4dcfee04a2082d5c

data/.github/workflows/ci.yml

@@ -1,6 +1,3 @@
-## This file is managed by Terraform.
-## Do not modify this file directly, as it may be overwritten.
-## Please open an issue instead.
 name: CI
 on: [push, pull_request]
 jobs:
@@ -8,12 +5,12 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        ruby: [2.7, '3.0', '3.1']
+        ruby: [2.5, 2.6, 2.7, '3.0', '3.1', '3.2', 'head', 'jruby']
     runs-on: ubuntu-latest
     steps:
     - uses: actions/checkout@v3
     - uses: ruby/setup-ruby@v1
       with:
         ruby-version: ${{ matrix.ruby }}
-        bundler-cache: true
+        bundler-cache: true # runs 'bundle install' and caches installed gems automatically
     - run: bundle exec rake

data/CHANGES.md

@@ -1,7 +1,21 @@
+# 2.1.3
 
+* Require `trailblazer-developer` 0.1 line which brings tracing performance increase by
+  factor 4-10.
+* Introduce `Operation.left` as an alias for `#fail`.
+* Better debugging API for the upcoming web debugger.
 
-# 2.1
+# 2.1.2
+
+* Use `trailblazer-activity-dsl-linear` >= 1.1.0.
+
+# 2.1.1
+
+* Use `trailblazer-activity-dsl-linear` >= 1.0.0.
+
+# 2.1.0
 
+* Remove `declarative` dependency.
 * Macros now always have to provide an `:id`. This was a bit fuzzy in 2.0.
 
 * Nested
@@ -23,27 +37,9 @@
 
     Always write to `options`.
 
-* self[] removed
 * Fixed `Guard` where procs could receive one argument, only. Guards follow the step interface: `Policy::Guard( ->(options, **) { .. } )
 * Removed `Operation::Callback` which was a poor idea and luckily no one was using it.
 
-TODO:
-document Task API and define step API
-deprecate step->(options) ?
-injectable, per-operation step arguments strategy?
-
-# 2.1.2
-
-* Use `trailblazer-activity-dsl-linear` >= 1.1.0.
-
-# 2.1.1
-
-* Use `trailblazer-activity-dsl-linear` >= 1.0.0.
-
-# 2.1.0
-
-* Remove `declarative` dependency.
-
 # 2.1.0.rc13
 
 * Use newest `macro` and `macro-context`.  They use symbols keys now everywhere.

data/README.md

@@ -1,203 +1,109 @@
 # Trailblazer
 
-_Trailblazer provides new high-level abstractions for Ruby frameworks. It gently enforces encapsulation, an intuitive code structure and approaches the modeling of complex business workflows with a functional mind-set._
+_Battle-tested Ruby framework to help structuring your business logic._
 
-[![Zulip chat](https://img.shields.io/badge/zulip-join_chat-brightgreen.svg)](https://trailblazer.zulipchat.com)
-[![TRB Newsletter](https://img.shields.io/badge/TRB-newsletter-lightgrey.svg)](http://trailblazer.to/newsletter/)
 [![Gem Version](https://badge.fury.io/rb/trailblazer.svg)](http://badge.fury.io/rb/trailblazer)
-[![Open Source Helpers](https://www.codetriage.com/trailblazer/trailblazer/badges/users.svg)](https://www.codetriage.com/trailblazer/trailblazer)
 
-## Documentation
-
-* **The current version is Trailblazer 2.1.** We do have [comprehensive API documenation](https://trailblazer.to/2.1/docs/trailblazer.html) ready for you. If you're new to TRB start with our [LEARN page](https://trailblazer.to/2.1/learn.html).
-* A migration guide from 2.0 can be found [on our website](https://trailblazer.to/2.1/docs/trailblazer.html#trailblazer-2-1-migration).
-* The [1.x documentation is here](http://trailblazer.to/2.0/gems/operation/1.1/index.html).
-
-Make sure to check out the new beginner's guide to learning Trailblazer. The [brand-new book](https://leanpub.com/buildalib) discusses all aspects in a step-wise approach you need to understand Trailblazer's mechanics and design ideas.
-
-<a href="https://leanpub.com/buildalib"><img src="https://trailblazer.to/images/2.1/buildalib-cover.png"></a>
-
-## Screencasts
-
-Watch our series of screencasts [**TRAILBLAZER TALES**](https://www.youtube.com/channel/UCi2P0tFMtjMUsWLYAD1Ezsw) if you prefer learning from videos!
-
-<a href="https://www.youtube.com/embed/9elpobV4HSw"><img src="https://trailblazer.to/images/2.1/01-operation-basics.png"></a>
-
-## Trailblazer In A Nutshell
-
-1. All business logic is encapsulated in [operations](#operation) (service objects).
-3. [Controllers](#controllers) instantly delegate to an operation. No business code in controllers, only HTTP-specific logic.
-4. [Models](#models) are persistence-only and solely define associations and scopes. No business code is to be found here. No validations, no callbacks.
-5. The presentation layer offers optional [view models](#views) (Cells) and [representers](#representers) for document APIs.
-6. More complex business flows and life-cycles are modeled using workflows.
-
-Want code? Jump [right here](#controllers)!
-
-## Mission
-
-While _Trailblazer_ offers you abstraction layers for all aspects of Ruby On Rails, it does _not_ missionize you. Wherever you want, you may fall back to the "Rails Way" with fat models, monolithic controllers, global helpers, etc. This is not a bad thing, but allows you to step-wise introduce Trailblazer's encapsulation in your app without having to rewrite it.
-
-Trailblazer is all about structure. It helps re-organize existing code into smaller components where different concerns are handled in separated classes.
+## What's Trailblazer?
 
-Again, you can pick which layers you want. Trailblazer doesn't impose technical implementations, it offers mature solutions for recurring problems in all types of Rails applications.
+Trailblazer introduces new abstraction layers into Ruby applications to help you structure your business logic.
 
-Trailblazer is no "complex web of objects and indirection". It solves many problems that have been around for years with a cleanly layered architecture. Only use what you like. And that's the bottom line.
+It ships with our canonical "service object" implementation called *operation*, many conventions, gems for testing, Rails support, optional form objects and much more.
 
-## Concepts over Technology
+## Should I use Trailblazer?
 
-Trailblazer offers you a new, more intuitive file layout in applications.
+Give us a chance if you say "yes" to this!
 
-```
-app
-├── concepts
-│   ├── song
-│   │   ├── operation
-│   │   │   ├── create.rb
-│   │   │   ├── update.rb
-│   │   ├── contract
-│   │   │   ├── create.rb
-│   │   │   ├── update.rb
-│   │   ├── cell
-│   │   │   ├── show.rb
-│   │   │   ├── index.rb
-│   │   ├── view
-│   │   │   ├── show.haml
-│   │   │   ├── index.rb
-│   │   │   ├── song.css.sass
-```
-
-Instead of grouping by technology, classes and views are structured by *concept*, and then by technology. A concept can relate to a model, or can be a completely abstract concern such as `invoicing`.
-
-Within a concept, you can have any level of nesting. For example, `invoicing/pdf/` could be one.
-
-
-## Architecture
-
-Trailblazer extends the conventional MVC stack in Rails. Keep in mind that adding layers doesn't necessarily mean adding more code and complexity.
-
-The opposite is the case: Controller, view and model become lean endpoints for HTTP, rendering and persistence. Redundant code gets eliminated by putting very little application code into the right layer.
+* You hate messy controller code but don't know where to put it?
+* Moving business code into the "fat model" gives you nightmares?
+* "Service objects" are great?
+* Anyhow, you're tired of 12 different "service object" implementations throughout your app?
+* You keep asking for additional layers such as forms, policies, decorators?
 
-![The Trailblazer stack.](https://raw.github.com/apotonick/trailblazer/master/doc/operation-2017.png)
+Yes? Then we got a well-seasoned framework for you: [Trailblazer](https://trailblazer.to/2.1).
 
-## Routing
+Here are the main concepts.
 
-Trailblazer uses Rails routing to map URLs to controllers, because it works.
-
-```ruby
-Rails.application.routes.draw do
-  resources :songs
-end
-```
-
-## Controllers
-
-Controllers are lean endpoints for HTTP. They do not contain any business logic. Actions immediately dispatch to an operation.
+## Operation
 
-```ruby
-class SongsController < ApplicationController
-  def create
-    run Song::Create # Song::Create is an operation class.
-  end
-end
-```
+The operation encapsulates business logic and is the heart of the Trailblazer architecture.
 
-The `#run` method invokes the operation. It allows you to run a conditional block of logic if the operation was successful.
+An operation is not just a monolithic replacement for your business code. It's a simple orchestrator between the form objects, models, your business code and all other layers needed to get the job done.
 
 ```ruby
-class SongsController < ApplicationController
-  def create
-    run Song::Create do |op|
-      return redirect_to(song_path op.model) # success!
+# app/concepts/song/operation/create.rb
+module Song::Operation
+  class Create < Trailblazer::Operation
+    step :create_model
+    step :validate
+    left :handle_errors
+    step :notify
+
+    def create_model(ctx, **)
+      # do whatever you feel like.
+      ctx[:model] = Song.new
     end
 
-    render :new # invalid. re-render form.
+    def validate(ctx, params:, **)
+      # ..
+    end
+    # ...
   end
 end
 ```
 
-Again, the controller only dispatchs to the operation and handles successful/invalid processing on the HTTP level. For instance by redirecting, setting flash messages, or signing in a user.
+The `step` DSL takes away the pain of flow control and error handling. You focus on _what_ happens: creating models, validating data, sending out notifications.
 
-[Learn more.](http://trailblazer.to/gems/operation/controller.html)
-
-## Operation
+### Control flow
 
-Operations encapsulate business logic and are the heart of a Trailblazer architecture.
+The operation takes care _when_ things happen: the flow control. Internally, this works as depicted in this beautiful diagram.
 
-The bare bones operation without any Trailblazery is implemented in [the `trailblazer-operation` gem](https://github.com/trailblazer/trailblazer-operation) and can be used without our stack.
+![Flow diagram of a typical operation.](https://github.com/trailblazer/trailblazer/blob/master/doc/song_operation_create.png?raw=true)
 
-Operations don't know about HTTP or the environment. You could use an operation in Rails, Hanami, or Roda, it wouldn't know.
-
-An operation is not just a monolithic replacement for your business code. It's a simple orchestrator between the form objects, models, your business code and all other layers needed to get the job done.
+The best part: the only way to invoke this operation is `Operation.call`. The single entry-point saves programmers from shenanigans with instances and internal state - it's proven to be an almost bullet-proof concept in the past 10 years.
 
 ```ruby
-class Song::Create < Trailblazer::Operation
-  step :model
-  step :validate
-
-  def model(ctx, **)
-    # do whatever you feel like.
-    ctx[:model] = Song.new
-  end
-
-  def validate(ctx, params:, **)
-    # ..
-  end
-end
-```
-
-Operations define the flow of their logic using the DSL and implement the particular steps with pure Ruby.
+result = Song::Operation::Create.(params: {title: "Hear Us Out", band: "Rancid"})
 
-You cannot instantiate them per design. The only way to invoke them is `call`.
-
-```ruby
-Song::Create.(params: {whatever: "goes", in: "here"})
+result.success? #=> true
+result[:model]  #=> #<Song title="Hear Us Out" ...>
 ```
 
-Their high degree of encapsulation makes them a [replacement for test factories](#tests), too.
+Data, computed values, statuses or models from within the operation run are exposed through the `result` object.
 
-[Learn more.](https://2019.trailblazer.to/2.1/docs/operation.html#operation-overview)
+Operations can be nested, use composition and inheritance patterns, provide [variable mapping](https://trailblazer.to/2.1/docs/activity#activity-variable-mapping) around each step, support dependency injection, and save you from reinventing the wheel - over and over, again.
 
-## Models
+Leveraging those functional mechanics, operations encourage a high degree of encapsulation while giving you all the conventions and tools for free (except for a bit of a learning curve).
 
-Models for persistence can be implemented using any ORM you fancy, for instance [ActiveRecord](https://github.com/rails/rails/tree/master/activerecord#active-record--object-relational-mapping-in-rails) or [Datamapper](http://datamapper.org/).
+### Tracing
 
-In Trailblazer, models are completely empty. They solely contain associations and finders. No business logic is allowed in models.
+In the past years, we learnt from some old mistakes and improved developer experience. As a starter, check out our built-in tracing!
 
 ```ruby
-class Song < ActiveRecord::Base
-  belongs_to :thing
-
-  scope :latest, lambda { all.limit(9).order("id DESC") }
-end
+result = Song::Operation::Create.wtf?(params: {title: "", band: "Rancid"})
 ```
 
-Only operations and views/cells can access models directly.
+![Tracing the internal flow of an operation.](https://github.com/trailblazer/trailblazer/blob/master/doc/song_operation_create_trace.png?raw=true)
 
-## Tests
+Within a second you know which step failed - a thing that might seem trivial, but when things grow and a deeply nested step in an iteration fails, you will start loving `#wtf?`! It has saved us days of debugging.
 
-In Trailblazer, you only have operation unit tests and integration smoke tests to test the operation/controller wiring.
+We even provide a [visual debugger](https://trailblazer.to/2.1/pro) to inspect traces on the webs.
 
-Operations completely replace the need for leaky factories.
+## There's a lot more
 
-```ruby
-describe Song::Update do
-  let(:song) { Song::Create.(song: {body: "[That](http://trailblazer.to)!"}) }
-end
-```
+All our abstraction layers such as [operations](https://trailblazer.to/2.1/docs/operation), [form objects](https://trailblazer.to/2.1/docs/reform.html), [view components](https://trailblazer.to/2.1/docs/cells.html), [test gems](https://trailblazer.to/2.1/docs/test) and much more are used in [hundreds of OSS projects](https://github.com/trailblazer/trailblazer/network/dependents) and commercial applications in the Ruby world.
 
-## Workflow
-Operations are a great way to clean up controllers and models. However, Trailblazer goes further and provides an approach to model entire life-cycles of business objects, such as "a song" or "the root user" using workflow ([`pro feature`](https://2019.trailblazer.to/2.1/docs/pro.html#pro-1)). Also, you don't have to use the DSL but can use the [`editor`](https://2019.trailblazer.to/2.1/docs/pro.html#pro-editor) instead (cool for more complex, long-running flows). Here comes a sample screenshot.
+We provide a [visual debugger](https://pro.trailblazer.to), a [BPMN editor](https://trailblazer.to/2.1/docs/workflow) for long-running business processes, [thorough documentation](https://trailblazer.to/2.1/docs/trailblazer.html) and a growing list of onboarding videos ([**TRAILBLAZER TALES**](https://www.youtube.com/channel/UCi2P0tFMtjMUsWLYAD1Ezsw)).
 
-<img src="http://2019.trailblazer.to/2.1/dist/img/flow.png">
+Trailblazer is both used for refactoring legacy apps (we support Ruby 2.5+) and helps big teams organizing, structuring and debugging modern, growing (Rails) applications.
 
-## Installation
+## Documentation
 
-The obvious needs to be in your `Gemfile`.
+* **The current version is Trailblazer 2.1.** We do have comprehensive [API documenation](https://trailblazer.to/2.1/docs/trailblazer.html) ready for you. If you're new to TRB start with our [LEARN page](https://trailblazer.to/2.1/learn.html).
+* A migration guide from 2.0 can be found [on our website](https://trailblazer.to/2.1/docs/trailblazer.html#trailblazer-2-1-migration).
+* The [1.x documentation is here](http://trailblazer.to/2.0/gems/operation/1.1/index.html).
 
-```ruby
-gem "trailblazer"
-gem "trailblazer-rails" # if you are in rails.
-gem "trailblazer-cells"
-```
+Make sure to check out the new beginner's guide to learning Trailblazer. The [new book](https://leanpub.com/buildalib) discusses all aspects in a step-wise approach you need to understand Trailblazer's mechanics and design ideas.
+
+![The new begginer's guide.](https://github.com/trailblazer/trailblazer/blob/master/doc/s_hero.png?raw=true)
 
-Cells is _not_ required per default! Add it if you use it, which is highly recommended.

data/lib/trailblazer/version.rb

@@ -1,5 +1,5 @@
 module Trailblazer
   module Version
-    VERSION = "2.1.2"
+    VERSION = "2.1.3"
   end
 end

data/test/test_helper.rb

@@ -1,38 +1,3 @@
-require "pp"
-require "delegate"
-require "trailblazer"
 require "minitest/autorun"
 
-# TODO: convert tests to non-rails.
-require "reform"
-require "reform/form/active_model/validations"
-Reform::Form.class_eval do
-  include Reform::Form::ActiveModel::Validations
-end
-# require "trailblazer/deprecation/context.rb"
-
-module Mock
-  class Result
-    def initialize(bool); @bool = bool end
-    def success?; @bool end
-    def errors; ["hihi"] end
-  end
-end
-
-module Test
-  module ReturnCall
-    def self.included(includer)
-      includer._insert :_insert, ReturnResult, {replace: Trailblazer::Operation::Result::Build}, ReturnResult, ""
-    end
-  end
-  ReturnResult = ->(last, input, options) { input }
-end
-
-Minitest::Spec::Operation = Trailblazer::Operation
-
-Memo = Struct.new(:id, :body) do
-  def self.find(id)
-    return new(id, "Yo!") if id
-    nil
-  end
-end
+require "trailblazer"

data/test/trailblazer_test.rb

@@ -0,0 +1,99 @@
+require "test_helper"
+require "reform/form/dry"
+require "trailblazer/macro"
+require "trailblazer/macro/contract"
+
+class TrailblazerTest < Minitest::Spec
+  Song = Struct.new(:title)
+
+
+  class Create < Trailblazer::Operation
+    class Form < Reform::Form
+      include Reform::Form::Dry
+      property :title
+
+      validation do
+        params do
+          required(:title).filled(min_size?: 2)
+        end
+      end
+    end
+
+    step Model(Song, :new)
+    step Contract::Build(constant: Form)
+    step Contract::Validate()
+    step Contract::Persist(method: :sync)
+  end
+
+  it do
+    result = nil
+
+    output, _ = capture_io do
+      result = Create.wtf?(params: {title: "Dead and Gone"})
+    end
+
+    assert_equal output, %(TrailblazerTest::Create
+|-- \e[32mStart.default\e[0m
+|-- \e[32mmodel.build\e[0m
+|-- \e[32mcontract.build\e[0m
+|-- contract.default.validate
+|   |-- \e[32mStart.default\e[0m
+|   |-- \e[32mcontract.default.params_extract\e[0m
+|   |-- \e[32mcontract.default.call\e[0m
+|   `-- End.success
+|-- \e[32mpersist.save\e[0m
+`-- End.success
+)
+    assert_equal result.success?, true
+    assert_equal result[:model].to_h, {:title=>"Dead and Gone"}
+
+  # invalid!
+      result = Create.wtf?(params: {})
+    output, _ = capture_io do
+      result = Create.wtf?(params: {})
+    end
+
+    assert_equal output, %(TrailblazerTest::Create
+|-- \e[32mStart.default\e[0m
+|-- \e[32mmodel.build\e[0m
+|-- \e[32mcontract.build\e[0m
+|-- contract.default.validate
+|   |-- \e[32mStart.default\e[0m
+|   |-- \e[32mcontract.default.params_extract\e[0m
+|   |-- \e[33mcontract.default.call\e[0m
+|   `-- End.failure
+`-- End.failure
+)
+
+    assert_equal result.success?, false
+    assert_equal result[:mode].to_h, {}
+  end
+end
+
+# Song = Struct.new(:title)
+# class Song
+#   module Operation
+#     class Create < Trailblazer::Operation
+#       step :create_model
+#       step :validate
+#       fail :handle_errors
+#       step :notify
+
+#       def create_model(ctx, **)
+#         # do whatever you feel like.
+#         ctx[:model] = Song.new
+#       end
+
+#       def validate(ctx, params:, **)
+#         # ..
+#       end
+
+#       def handle_errors(ctx, **)
+#         true
+#       end
+#     end
+
+#   end
+# end
+
+# Song::Operation::Create.wtf?(params: {})

data/trailblazer.gemspec

@@ -7,9 +7,8 @@ Gem::Specification.new do |spec|
   spec.version       = Trailblazer::Version::VERSION
   spec.authors       = ["Nick Sutterer"]
   spec.email         = ["apotonick@gmail.com"]
-  spec.description   = %q{A high-level architecture introducing new abstractions such as operations and control flow, form objects and policies.}
-  spec.summary       = %q{A high-level architecture for Ruby and Rails.}
-  spec.homepage      = "http://trailblazer.to"
+  spec.summary       = %q{Ruby framework for structuring your business logic.}
+  spec.homepage      = "https://trailblazer.to"
   spec.license       = "LGPL-3.0"
   spec.metadata      = {
     "bug_tracker_uri"   => "https://github.com/trailblazer/trailblazer/issues",
@@ -27,14 +26,17 @@ Gem::Specification.new do |spec|
   spec.test_files    = `git ls-files -z test`.split("\x0")
   spec.require_paths = ["lib"]
 
-  spec.add_dependency "trailblazer-macro",          ">= 2.1.12", "< 2.2.0"
+  spec.add_dependency "trailblazer-macro",          ">= 2.1.15", "< 2.2.0"
+  spec.add_dependency "trailblazer-developer",      ">= 0.1.0", "< 0.2.0"
   spec.add_dependency "trailblazer-macro-contract", ">= 2.1.4", "< 2.2.0"
   spec.add_dependency "trailblazer-operation",      ">= 0.9.0", "< 1.0.0"
+  spec.add_dependency "trailblazer-activity-dsl-linear", ">= 1.2.3", "< 1.3.0" # this can be removed at some point.
 
   spec.add_development_dependency "bundler"
   spec.add_development_dependency "rake"
   spec.add_development_dependency "minitest"
   spec.add_development_dependency "minitest-line"
+  spec.add_development_dependency "dry-validation"
 
-  spec.required_ruby_version = '>= 2.1.0'
+  spec.required_ruby_version = '>= 2.5.0'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: trailblazer
 version: !ruby/object:Gem::Version
-  version: 2.1.2
+  version: 2.1.3
 platform: ruby
 authors:
 - Nick Sutterer
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2022-12-14 00:00:00.000000000 Z
+date: 2023-06-15 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: trailblazer-macro
@@ -16,7 +16,7 @@ dependencies:
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: 2.1.12
+        version: 2.1.15
     - - "<"
       - !ruby/object:Gem::Version
         version: 2.2.0
@@ -26,10 +26,30 @@ dependencies:
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: 2.1.12
+        version: 2.1.15
     - - "<"
       - !ruby/object:Gem::Version
         version: 2.2.0
+- !ruby/object:Gem::Dependency
+  name: trailblazer-developer
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 0.1.0
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: 0.2.0
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 0.1.0
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: 0.2.0
 - !ruby/object:Gem::Dependency
   name: trailblazer-macro-contract
   requirement: !ruby/object:Gem::Requirement
@@ -70,6 +90,26 @@ dependencies:
     - - "<"
       - !ruby/object:Gem::Version
         version: 1.0.0
+- !ruby/object:Gem::Dependency
+  name: trailblazer-activity-dsl-linear
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 1.2.3
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: 1.3.0
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 1.2.3
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: 1.3.0
 - !ruby/object:Gem::Dependency
   name: bundler
   requirement: !ruby/object:Gem::Requirement
@@ -126,8 +166,21 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: '0'
-description: A high-level architecture introducing new abstractions such as operations
-  and control flow, form objects and policies.
+- !ruby/object:Gem::Dependency
+  name: dry-validation
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+description: 
 email:
 - apotonick@gmail.com
 executables: []
@@ -136,9 +189,6 @@ extra_rdoc_files: []
 files:
 - ".github/dependabot.yml"
 - ".github/workflows/ci.yml"
-- ".github/workflows/ci_jruby.yml"
-- ".github/workflows/ci_legacy.yml"
-- ".github/workflows/ci_truffleruby.yml"
 - ".gitignore"
 - CHANGES.md
 - COMM-LICENSE
@@ -151,8 +201,9 @@ files:
 - lib/trailblazer.rb
 - lib/trailblazer/version.rb
 - test/test_helper.rb
+- test/trailblazer_test.rb
 - trailblazer.gemspec
-homepage: http://trailblazer.to
+homepage: https://trailblazer.to
 licenses:
 - LGPL-3.0
 metadata:
@@ -171,7 +222,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: 2.1.0
+      version: 2.5.0
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
@@ -181,6 +232,7 @@ requirements: []
 rubygems_version: 3.2.3
 signing_key: 
 specification_version: 4
-summary: A high-level architecture for Ruby and Rails.
+summary: Ruby framework for structuring your business logic.
 test_files:
 - test/test_helper.rb
+- test/trailblazer_test.rb

data/.github/workflows/ci_jruby.yml

@@ -1,19 +0,0 @@
-## This file is managed by Terraform.
-## Do not modify this file directly, as it may be overwritten.
-## Please open an issue instead.
-name: CI JRuby
-on: [push, pull_request]
-jobs:
-  test:
-    strategy:
-      fail-fast: false
-      matrix:
-        ruby: [jruby, jruby-head]
-    runs-on: ubuntu-latest
-    steps:
-    - uses: actions/checkout@v3
-    - uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: ${{ matrix.ruby }}
-        bundler-cache: true
-    - run: bundle exec rake

data/.github/workflows/ci_legacy.yml

@@ -1,19 +0,0 @@
-## This file is managed by Terraform.
-## Do not modify this file directly, as it may be overwritten.
-## Please open an issue instead.
-name: CI with EOL ruby versions
-on: [push, pull_request]
-jobs:
-  test:
-    strategy:
-      fail-fast: false
-      matrix:
-        ruby: [2.5, 2.6]
-    runs-on: ubuntu-latest
-    steps:
-    - uses: actions/checkout@v3
-    - uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: ${{ matrix.ruby }}
-        bundler-cache: true
-    - run: bundle exec rake

data/.github/workflows/ci_truffleruby.yml

@@ -1,19 +0,0 @@
-## This file is managed by Terraform.
-## Do not modify this file directly, as it may be overwritten.
-## Please open an issue instead.
-name: CI TruffleRuby
-on: [push, pull_request]
-jobs:
-  test:
-    strategy:
-      fail-fast: false
-      matrix:
-        ruby: [truffleruby, truffleruby-head]
-    runs-on: ubuntu-latest
-    steps:
-    - uses: actions/checkout@v3
-    - uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: ${{ matrix.ruby }}
-        bundler-cache: true
-    - run: bundle exec rake