f_service 0.3.0 → 0.4.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 6cb29d87cf5c970b2b185ed2c3da41020f40122e2d0857af068302fb32e55400
-  data.tar.gz: 27a89660bb6d1e65d537f5d6617cc8175f600ab71efca79f65875a1b6adf0c97
+  metadata.gz: 1e6e4ea7905315820d4149138a6d0acfbcb013cde481b34cb0cbd95247aef439
+  data.tar.gz: 7abcb86eaf3080a9c1e8d6bfaca8b5c8a70a932ba0e57fd55e9bd88f479d538c
 SHA512:
-  metadata.gz: 2b444953aee676163a2b076d814b3cc801b0808a30660c4edd2f19172754d58c41a7fcb3129a52cf95c1a0fdb8546419a55a8101b6882459673cd647d520f660
-  data.tar.gz: 0e2f10e1ad6cf4ba7ba2375b2302661429721b7bf4023afcb1559909205eb7e8f013efbb3da07c4b7926b2e967592c31a6c930ca6d6e69b195bba97342407b69
+  metadata.gz: 36ec32dab3e5b223996963426298949403bf606fccd1d58c26362d1c38de8e46a5717f4639264709aee03d11b78b960f270e4db3b003f9688b57b2e0456bb958
+  data.tar.gz: 42d233650b876ca35f68b99d2985c4044b1e2989779e9817c9ea20677ecd3bf696e2d22bf7c9c0238b1803ccf74501af7e65ff1ccd70c4878b11be941218fba1

data/CHANGELOG.md

@@ -4,11 +4,22 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## Unreleased (master)
-<!-- ### Added -->
-<!-- ### Changed -->
-<!-- ### Removed -->
----
+## [0.4.0](https://github.com/Fretadao/f_service/compare/v0.3.1...v0.4.0) (2026-08-19)
+
+
+### ⚠ BREAKING CHANGES
+
+* Failure#then and Success#then were removed; use #and_then, which has always been their alias. Base#success, Base#failure and Base#result were removed; use #Success, #Failure and #Check. Result#type was removed; use #types. The mock_service `type:` argument was removed; use `types:` with an array.
+
+### Features
+
+* remove deprecated Failure#then, Success#then and the 0.2.0 leftovers ([#63](https://github.com/Fretadao/f_service/issues/63)) ([69b4e80](https://github.com/Fretadao/f_service/commit/69b4e8099cfdb9850ecab656779436ac9cf16d09))
+
+## 0.3.1
+### Added
+ - Drop Support to Ruby 2.6 and 2.7
+ - Add Support to Ruby 3.2 and 3.3
+ - Changed and_error to use a matcher instead of equality comparation #51
 
 ## 0.3.0
 ### Added

data/README.md

@@ -23,9 +23,14 @@ It uses the Result monad for handling operations.
 
 Add this line to your application's Gemfile:
 
+<!-- x-release-please-start-version -->
 ```ruby
-gem 'f_service'
+gem 'f_service', '~> 0.4.0'
 ```
+<!-- x-release-please-end-version -->
+
+> The version above is kept current automatically on every release; pin to
+> whichever version you prefer.
 
 And then execute:
 
@@ -64,11 +69,12 @@ You can optionally specify a list of types which represents that result and a va
 class User::Create < FService::Base
   # ...
   def run
-    return Failure(:no_name, :invalid_attribute) if @name.nil?
+    return Failure(:invalid_name, data: { name: ["can't be blank"] }) if @name.nil?
 
     user = UserRepository.create(name: @name)
+
     if user.save
-      Success(:success, :created, data: user)
+      Success(:created, data: user)
     else
       Failure(:creation_failed, data: user.errors)
     end
@@ -78,6 +84,11 @@ end
 
 > Remember, you **have** to return an `FService::Result` at the end of your services.
 
+> Always give your results a type. It says what happened, not just whether it worked, so
+> callers can branch on the reason and a failure is readable in a log without opening the
+> service. Pass the payload in `data:`, including on failures — otherwise `#error` is `nil`
+> and whoever serializes it has nothing to show.
+
 ### Using your service
 
 To run your service, use the method `#call` provided by `FService::Base`. We like to use the [implicit call](https://stackoverflow.com/a/19108981/8650655), but you can use it in the form you like most.
@@ -112,7 +123,7 @@ class UsersController < BaseController
 end
 ```
 
-> Note that you're not limited to using services inside controllers. They're just PORO's (Play Old Ruby Objects), so you can use in controllers, models, etc. (even other services!).
+> Note that you're not limited to using services inside controllers. They're just PORO's (Plain Old Ruby Objects), so you can use in controllers, models, etc. (even other services!).
 
 ### Pattern matching
 
@@ -121,79 +132,77 @@ The code above could be rewritten using the `#on_success` and `#on_failure` hook
 ```ruby
 class UsersController < BaseController
   def create
-    User::Create.(user_params)
-                .on_success { |value| return json_success(value) }
-                .on_failure { |error| return json_error(error) }
+    User::Create
+      .call(user_params)
+      .on_success { |user| return json_success(user) }
+      .on_failure { |errors| return json_error(errors) }
   end
 end
 ```
 
-Or else it is possible to specify an unhandled option to ensure that the callback will process that message anyway the
-error.
+> You can ignore any of the callbacks, if you want to.
 
-```ruby
-class UsersController < BaseController
-  def create
-    User::Create.(user_params)
-                .on_success(unhandled: true) { |value| return json_success(value) }
-                .on_failure(unhandled: true) { |error| return json_error(error) }
-  end
-end
-```
+Once you start matching specific types (below), a result whose type none of the hooks
+mention falls through untouched. Pass `unhandled: true` to run a callback for exactly those
+leftovers:
 
 ```ruby
 class UsersController < BaseController
   def create
-    User::Create.(user_params)
-                .on_success { |value| return json_success(value) }
-                .on_failure { |error| return json_error(error) }
+    User::Create
+      .call(user_params)
+      .on_success(:created) { |user| return json_success(user) }
+      .on_failure(unhandled: true) { |errors| return json_error(errors) }
   end
 end
 ```
 
-> You can ignore any of the callbacks, if you want to.
-
 Going further, you can match the Result type, in case you want to handle them differently:
 
 ```ruby
 class UsersController < BaseController
   def create
-    User::Create.(user_params)
-                .on_success(:user_created) { |value| return json_success(value) }
-                .on_success(:user_already_exists) { |value| return json_success(value) }
-                .on_failure(:invalid_data) { |error| return json_error(error) }
-                .on_failure(:critical_error) do |error|
-                  MyLogger.report_failure(error)
-
-                  return json_error(error)
-                end
+    User::Create
+      .call(user_params)
+      .on_success(:created) { |user| return json_success(user) }
+      .on_failure(:invalid_name) { |errors| return json_error(errors) }
+      .on_failure(:creation_failed) do |errors|
+        MyLogger.report_failure(errors)
+
+        return json_error(errors)
+      end
   end
 end
 ```
 
 It's possible to provide multiple types to the hooks too. If the result type matches any of the given types,
-the hook will run.
+the hook will run. Say the service also answers `Success(:already_exists, data: user)` when the
+name is taken — both outcomes are fine for the caller:
 
 ```ruby
 class UsersController < BaseController
   def create
-    User::Create.(user_params)
-                .on_success(:user_created, :user_already_exists) { |value| return json_success(value) }
-                .on_failure(:invalid_data) { |error| return json_error(error) }
-                .on_failure(:critical_error) do |error|
-                  MyLogger.report_failure(error)
-
-                  return json_error(error)
-                end
+    User::Create
+      .call(user_params)
+      .on_success(:created, :already_exists) { |user| return json_success(user) }
+      .on_failure(:invalid_name) { |errors| return json_error(errors) }
+      .on_failure(:creation_failed) do |errors|
+        MyLogger.report_failure(errors)
+
+        return json_error(errors)
+      end
   end
 end
 ```
 
-### Types precedence
+### Type precedence
 
-FService matches types from left to right, from more specific to more generic.
-Example (:unprocessable_entity, :client_error, :http_response)
-Then, result will match first :unprocessable_entity, after :client_error, after :http_response, then not matched.
+FService matches the service's types from left to right, from more specific to more generic.
+For example, the following result `Failure(:unprocessable_entity, :client_error, :http_response)` will match in the following order:
+1. `:unprocessable_entity`;
+2. `:client_error`;
+3. `:http_response`;
+4. unmatched block;
 
 ### Chaining services
 
@@ -203,9 +212,10 @@ If some step fails, it will short circuit the call chain.
 ```ruby
 class UsersController < BaseController
   def create
-    result = User::Create.(user_params)
-                         .and_then { |user| User::Login.(user) }
-                         .and_then { |user| User::SendWelcomeEmail.(user) }
+    result = User::Create
+      .call(user_params)
+      .and_then { |user| User::Login.(user) }
+      .and_then { |user| User::SendWelcomeEmail.(user) }
 
     if result.successful?
       json_success(result.value)
@@ -221,17 +231,23 @@ You can use the `.to_proc` method on FService::Base to avoid explicit inputs whe
 ```ruby
 class UsersController < BaseController
   def create
-    result = User::Create.(user_params)
-                         .and_then(&User::Login)
-                         .and_then(&User::SendWelcomeEmail)
+    result = User::Create
+      .call(user_params)
+      .and_then(&User::Login)
+      .and_then(&User::SendWelcomeEmail)
     # ...
   end
 end
 ```
 
+> **Coming from 0.2.x?** `Success#then` and `Failure#then` were deprecated in 0.3.0 and
+> removed in 0.4.0. Use `#and_then`, which has always been their alias and behaves
+> identically. Note that `#then` also exists on every Ruby object since 2.6, so a leftover
+> call does not raise — it silently yields the Result itself instead of its value.
+
 ### `Check` and `Try`
 
-You can use `Check` to converts a boolean to a Result, truthy values map to `Success`, and falsey values map to `Failures`:
+You can use `Check` to convert a boolean into a Result: truthy values map to `Success`, falsey values to `Failure`.
 
 ```ruby
 Check(:math_works) { 1 < 2 }
@@ -245,71 +261,116 @@ Check(:math_works) { 1 > 2 }
 using the parameter `catch`.
 
 ```ruby
-class IHateEvenNumbers < FService::Base
+class Number::DrawOdd < FService::Base
   def run
-    Try(:rand_int) do
-      n = rand(1..10)
-      raise "Yuck! It's a #{n}" if n.even?
+    Try(:drawn_number) do
+      drawn_number = rand(1..10)
+      raise "Yuck! It's a #{drawn_number}" if drawn_number.even?
 
-      n
+      drawn_number
     end
   end
 end
 
-IHateEvenNumbers.call
-# => #<Success @value=9, @types=[:rand_int]>
+Number::DrawOdd.call
+# => #<Success @value=9, @types=[:drawn_number]>
 
-IHateEvenNumbers.call
-# => #<Failure @error=#<RuntimeError: Yuck! It's a 4>, @types=[:rand_int]>
+Number::DrawOdd.call
+# => #<Failure @error=#<RuntimeError: Yuck! It's a 4>, @types=[:drawn_number]>
 ```
 
 ## Testing
 
-We provide some helpers and matchers to make ease to test code envolving Fservice services.
+We provide helpers and matchers to make it easier to test code involving FService services.
 
-To make available in the system, in the file 'spec/spec_helper.rb' or 'spec/rails_helper.rb'
+To make them available, add the following require to `spec/spec_helper.rb` or
+`spec/rails_helper.rb`:
 
-add the folowing require:
-
-```rb
+```ruby
 require 'f_service/rspec'
 ```
 
 ### Mocking a result
 
-```
-mock_service(Uer::Create)
-# => Mocks a successful result with all values nil
+`mock_service` stubs the service's `#call` and returns the Result you describe. It is a stub,
+not a message expectation: it does not assert that the service was called, so add your own
+`expect(...).to have_received(:call)` when that is the point of the test.
 
-mock_service(Uer::Create, result: :success)
-# => Mocks a successful result with all values nil
+```ruby
+mock_service(User::Create)
+# => stubs a successful result, with no types and a nil value
 
-mock_service(Uer::Create, result: :success, types: [:created, :success])
-# => Mocks a successful result with type created
+mock_service(User::Create, result: :success, types: [:created])
+# => stubs a Success typed :created
 
-mock_service(Uer::Create, result: :success, types: :created, value: instance_spy(User))
-# => Mocks a successful result with type created and a value
+mock_service(User::Create, result: :success, types: [:created], value: instance_spy(User))
+# => stubs a Success typed :created carrying a value
 
-mock_service(Uer::Create, result: :failure)
-# => Mocs a failure with all nil values
+mock_service(User::Create, result: :failure, types: [:invalid_name])
+# => stubs a Failure typed :invalid_name, with a nil error
 
-mock_service(User::Create, result: :failure, types: [:unprocessable_entity, :client_error])
-# => Mocs a failure with a failure type
+mock_service(
+  User::Create,
+  result: :failure,
+  types: [:invalid_name],
+  value: { name: ["can't be blank"] }
+)
+# => stubs a Failure typed :invalid_name carrying an error
+```
 
-mock_service(User::Create, result: :failure, types: [:unprocessable_entity, :client_error], value: { name: ["can't be blank"] })
-# => Mocs a failure with a failure type and an error value
+> `value:` fills `#value` on a Success and `#error` on a Failure — it is the payload either
+> way. `types:` also accepts a bare symbol, but an array reads consistently. The deprecated
+> singular `type:` argument was removed in 0.4.0.
+
+Need the Result object itself rather than a stub — to pass it around in a unit test, say?
+`f_service_result` builds one:
+
+```ruby
+result = f_service_result(:failure, { name: ["can't be blank"] }, [:invalid_name])
+# => #<Failure @error={name: ["can't be blank"]}, @types=[:invalid_name]>
 ```
 
 ### Matching a result
 
-```rb
+```ruby
 expect(User::Create.(name: 'Joe')).to have_succeed_with(:created)
 
 expect(User::Create.(name: 'Joe')).to have_succeed_with(:created).and_value(an_instance_of(User))
 
-expect(User::Create.(name: nil)).to have_failed_with(:invalid_attributes)
+expect(User::Create.(name: nil)).to have_failed_with(:invalid_name)
+
+expect(User::Create.(name: nil))
+  .to have_failed_with(:invalid_name).and_error({ name: ["can't be blank"] })
 
-expect(User::Create.(name: nil)).to have_failed_with(:invalid_attributes).and_error({ name: ["can't be blank"] })
+expect(User::Create.(name: nil))
+  .to have_failed_with(:invalid_name).and_error(a_hash_including(name: ["can't be blank"]))
+```
+
+> The matchers compare the type list for **equality**, not inclusion. A service answering
+> `Success(:created, :persisted)` is matched by `have_succeed_with(:created, :persisted)` —
+> `have_succeed_with(:created)` alone fails. Name every type the result carries.
+
+Putting it together, a spec for the service built above:
+
+```ruby
+RSpec.describe User::Create do
+  subject(:create_user) { described_class.call(name: name) }
+
+  context 'when the name is given' do
+    let(:name) { 'Joe' }
+
+    it { is_expected.to have_succeed_with(:created).and_value(an_instance_of(User)) }
+  end
+
+  context 'when the name is missing' do
+    let(:name) { nil }
+
+    it 'fails naming the offending attribute' do
+      expect(create_user)
+        .to have_failed_with(:invalid_name).and_error(a_hash_including(:name))
+    end
+  end
+end
 ```
 
 ## API Docs
@@ -320,11 +381,17 @@ You can access the API docs [here](https://www.rubydoc.info/gems/f_service/).
 
 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 allows you to experiment.
 
-To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+To install this gem onto your local machine, run `bundle exec rake install`.
+
+Releases are automated: the version, the `CHANGELOG.md`, the git tag and the push to
+[rubygems.org](https://rubygems.org) are all derived from
+[Conventional Commits](https://www.conventionalcommits.org/) by release-please. There
+is no version to edit and no release command to run by hand — see
+[CONTRIBUTING.md](CONTRIBUTING.md).
 
 ## Contributing
 
-Bug reports and pull requests are welcome on GitHub at https://github.com/Fretadao/f_service.
+Bug reports and pull requests are welcome on GitHub at https://github.com/Fretadao/f_service. Read [CONTRIBUTING.md](CONTRIBUTING.md) first — it covers the commit conventions the release automation depends on.
 
 ## License
 

data/f_service.gemspec

@@ -19,20 +19,29 @@ Gem::Specification.new do |spec|
 
   spec.homepage = 'https://github.com/Fretadao/f_service'
   spec.license  = 'MIT'
+  spec.required_ruby_version = '>= 3.0.0'
 
   spec.metadata['homepage_uri']    = spec.homepage
   spec.metadata['source_code_uri'] = 'https://github.com/Fretadao/f_service'
   spec.metadata['documentation_uri'] = 'https://www.rubydoc.info/gems/f_service'
   spec.metadata['changelog_uri'] = 'https://github.com/Fretadao/f_service/blob/master/CHANGELOG.md'
 
-  # 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.
+  # Ship only what a consumer of the gem needs: the library, the docs and the
+  # licence. Everything else tracked in the repository is development tooling and
+  # was being packaged until now — CI workflows, git hooks, the Gemfile, and so on.
+  development_only = %r{
+    ^(bin|test|spec|features)/    # console/setup scripts and test suites
+    | ^\.git                      # .gitignore, .github/, .githooks/
+    | ^\.rubocop                  # linter configuration
+    | ^(Gemfile|Rakefile)         # development entrypoints
+    | ^CONTRIBUTING               # contributor documentation
+    | release-please              # release automation configuration
+  }x
+
   spec.files = Dir.chdir(File.expand_path(__dir__)) do
-    `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
+    `git ls-files -z`.split("\x0").grep_v(development_only)
   end
   spec.bindir        = 'exe'
   spec.executables   = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
   spec.require_paths = ['lib']
-
-  spec.add_development_dependency 'bundler', '~> 2.0'
 end

data/lib/f_service/base.rb

@@ -78,36 +78,6 @@ module FService
       raise NotImplementedError, 'Services must implement #run'
     end
 
-    # Returns a successful operation.
-    # You'll probably want to return this inside {#run}.
-    #
-    #
-    # @example
-    #   class User::ValidateAge < FService::Base
-    #     def initialize(age:)
-    #       @age = age
-    #     end
-    #
-    #     def run
-    #       return failure(status: 'No age given!', data: @age) if age.blank?
-    #       return failure(status: 'Too young!', data: @age) if age < 18
-    #
-    #       success(status: 'Valid age.', data: @age)
-    #     end
-    #   end
-    #
-    # @deprecated Use {#Success} instead.
-    # @return [Result::Success] a successful operation
-    def success(data = nil)
-      FService.deprecate!(
-        name: "#{self.class}##{__method__}",
-        alternative: '#Success',
-        from: caller[0]
-      )
-
-      Result::Success.new(data)
-    end
-
     # Returns a successful result.
     # You can optionally specify a list of types and a value for your result.
     # You'll probably want to return this inside {#run}.
@@ -229,67 +199,5 @@ module FService
     rescue *catch => e
       Failure(*types, data: e)
     end
-
-    # Returns a failed operation.
-    # You'll probably want to return this inside {#run}.
-    # @example
-    #   class User::ValidateAge < FService::Base
-    #     def initialize(age:)
-    #       @age = age
-    #     end
-    #
-    #     def run
-    #       return failure(status: 'No age given!', data: @age) if age.blank?
-    #       return failure(status: 'Too young!', data: @age) if age < 18
-    #
-    #       success(status: 'Valid age.', data: @age)
-    #     end
-    #   end
-    #
-    # @deprecated Use {#Failure} instead.
-    # @return [Result::Failure] a failed operation
-    def failure(data = nil)
-      FService.deprecate!(
-        name: "#{self.class}##{__method__}",
-        alternative: '#Failure',
-        from: caller[0]
-      )
-
-      Result::Failure.new(data)
-    end
-
-    # Return either {Result::Failure Success} or {Result::Failure Failure}
-    # given the condition.
-    #
-    # @example
-    #   class YearIsLeap < FService::Base
-    #     def initialize(year:)
-    #       @year = year
-    #     end
-    #
-    #     def run
-    #       return failure(status: 'No year given!', data: @year) if @year.nil?
-    #
-    #       result(leap?, @year)
-    #     end
-    #
-    #     private
-    #
-    #     def leap?
-    #       ((@year % 4).zero? && @year % 100 != 0) || (@year % 400).zero?
-    #     end
-    #   end
-    #
-    # @deprecated Use {#Check} instead.
-    # @return [Result::Success, Result::Failure]
-    def result(condition, data = nil)
-      FService.deprecate!(
-        name: "#{self.class}##{__method__}",
-        alternative: '#Check',
-        from: caller[0]
-      )
-
-      condition ? success(data) : failure(data)
-    end
   end
 end

data/lib/f_service/result/base.rb

@@ -22,13 +22,6 @@ module FService
         @matching_types = []
       end
 
-      # Implements old attribute type. Its deprecated in favor of using types.
-      def type
-        FService.deprecate!(name: "#{self.class}##{__method__}", alternative: '#types', from: caller[0])
-
-        types.size == 1 ? types.first : Array(@matching_types).first
-      end
-
       # This hook runs if the result is successful.
       # Can receive one or more types to be checked before running the given block.
       #

data/lib/f_service/result/failure.rb

@@ -110,12 +110,6 @@ module FService
         self
       end
 
-      # See #and_then
-      def then
-        FService.deprecate!(name: "#{self.class}##{__method__}", alternative: '#and_then', from: caller[0])
-        and_then
-      end
-
       # Outputs a string representation of the object
       #
       #

data/lib/f_service/result/success.rb

@@ -83,13 +83,6 @@ module FService
         yield(*to_ary)
       end
 
-      # See #and_then
-      def then(&block)
-        FService.deprecate!(name: "#{self.class}##{__method__}", alternative: '#and_then', from: caller[0])
-
-        and_then(&block)
-      end
-
       # Returns itself to the given block.
       # Use this to chain multiple actions or service calls (only valid when they return a Result).
       # It works just like the `.and_then` method, but only runs if service is a Failure.

data/lib/f_service/rspec/support/helpers/result.rb

@@ -12,17 +12,8 @@ module FServiceResultHelpers
   end
 
   # Mock a Fservice service call returning a result.
-  def mock_service(service, result: :success, value: nil, type: :not_passed, types: [])
-    result_types = Array(types)
-
-    if type != :not_passed
-      alternative = "mock_service(..., types: [#{type.inspect}])"
-      name = 'mock_service'
-      FService.deprecate_argument_name(name: name, argument_name: :type, alternative: alternative, from: caller[0])
-      result_types = Array(type)
-    end
-
-    service_result = f_service_result(result, value, result_types)
+  def mock_service(service, result: :success, value: nil, types: [])
+    service_result = f_service_result(result, value, Array(types))
     allow(service).to receive(:call).and_return(service_result)
   end
 end

data/lib/f_service/rspec/support/matchers/result.rb

@@ -6,7 +6,7 @@ RSpec::Matchers.define :have_failed_with do |*expected_types|
   match do |actual|
     matched = actual.is_a?(FService::Result::Failure) && actual.types == expected_types
 
-    matched &&= actual.error == @expected_error if defined?(@expected_error)
+    matched &&= values_match?(@expected_error, actual.error) if defined?(@expected_error)
 
     matched
   end

data/lib/f_service/version.rb

@@ -2,5 +2,5 @@
 
 module FService
   # Current version of the gem
-  VERSION = '0.3.0'
+  VERSION = '0.4.0'
 end

metadata

@@ -1,29 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: f_service
 version: !ruby/object:Gem::Version
-  version: 0.3.0
+  version: 0.4.0
 platform: ruby
 authors:
 - Fretadao Tech Team
-autorequire: 
 bindir: exe
 cert_chain: []
-date: 2023-05-22 00:00:00.000000000 Z
-dependencies:
-- !ruby/object:Gem::Dependency
-  name: bundler
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '2.0'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '2.0'
+date: 1980-01-02 00:00:00.000000000 Z
+dependencies: []
 description: |2
       FService is a small gem that provides a base class for your services (aka operations).
       The goal is to make services simpler, safer and more composable.
@@ -34,18 +19,9 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- ".github/.dependabot.yml"
-- ".github/workflows/tests-and-linter.yml"
-- ".gitignore"
-- ".rubocop.yml"
 - CHANGELOG.md
-- Gemfile
-- Gemfile.lock
 - LICENSE
 - README.md
-- Rakefile
-- bin/console
-- bin/setup
 - f_service.gemspec
 - lib/f_service.rb
 - lib/f_service/base.rb
@@ -69,7 +45,6 @@ metadata:
   source_code_uri: https://github.com/Fretadao/f_service
   documentation_uri: https://www.rubydoc.info/gems/f_service
   changelog_uri: https://github.com/Fretadao/f_service/blob/master/CHANGELOG.md
-post_install_message: 
 rdoc_options: []
 require_paths:
 - lib
@@ -77,15 +52,14 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: '0'
+      version: 3.0.0
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.3.5
-signing_key: 
+rubygems_version: 3.6.9
 specification_version: 4
 summary: A small, monad-based service class
 test_files: []

data/.github/.dependabot.yml

@@ -1,8 +0,0 @@
-version: 2
-updates:
-- package-ecosystem: bundler
-  directory: "/"
-  schedule:
-    interval: daily
-    time: "09:00"
-  open-pull-requests-limit: 10

data/.github/workflows/tests-and-linter.yml

@@ -1,28 +0,0 @@
-name: Ruby
-
-on:
-  push:
-    branches: [master]
-  pull_request:
-    branches: [master]
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    strategy:
-      matrix:
-        ruby: [2.6, 2.7, 3.0, 3.1]
-
-    steps:
-      - uses: actions/checkout@v2
-      - name: Set up Ruby ${{ matrix.ruby }}
-        uses: ruby/setup-ruby@v1
-        with:
-          ruby-version: ${{ matrix.ruby }}
-      - name: Build and test with Rake
-        run: |
-          gem install bundler
-          bundle install --jobs 4 --retry 3
-          bundle exec rake
-      - name: Rubocop Linter Action
-        run: bundle exec rubocop --parallel

data/.gitignore

@@ -1,58 +0,0 @@
-*.gem
-*.rbc
-/.config
-/coverage/
-/InstalledFiles
-/pkg/
-/spec/reports/
-/spec/examples.txt
-/test/tmp/
-/test/version_tmp/
-/tmp/
-
-# Used by dotenv library to load environment variables.
-# .env
-
-# Ignore Byebug command history file.
-.byebug_history
-
-## Specific to RubyMotion:
-.dat*
-.repl_history
-build/
-*.bridgesupport
-build-iPhoneOS/
-build-iPhoneSimulator/
-
-## Specific to RubyMotion (use of CocoaPods):
-#
-# We recommend against adding the Pods directory to your .gitignore. However
-# you should judge for yourself, the pros and cons are mentioned at:
-# https://guides.cocoapods.org/using/using-cocoapods.html#should-i-check-the-pods-directory-into-source-control
-#
-# vendor/Pods/
-
-## Documentation cache and generated files:
-/.yardoc/
-/_yardoc/
-/doc/
-/rdoc/
-
-## Environment normalization:
-/.bundle/
-/vendor/bundle
-/lib/bundler/man/
-
-# for a library or gem, you might want to ignore these files since the code is
-# intended to run in multiple environments; otherwise, check them in:
-# Gemfile.lock
-# .ruby-version
-# .ruby-gemset
-
-# unless supporting rvm < 1.11.0 or doing something fancy, ignore this:
-.rvmrc
-
-# Used by RuboCop. Remote config files pulled in from inherit_from directive.
-# .rubocop-https?--*
-
-.rspec_status

data/.rubocop.yml

@@ -1,33 +0,0 @@
-require:
-  - rubocop-rspec
-
-AllCops:
-  NewCops: enable
-
-Layout/LineLength:
-  Max: 120
-
-Metrics/BlockLength:
-  Exclude:
-    - "spec/**/*"
-
-Style/DocumentationMethod:
-  Enabled: true
-
-Naming/MethodName:
-  Exclude:
-    - lib/f_service/base.rb
-
-RSpec/ContextWording:
-  Prefixes:
-    - and
-    - but
-    - when
-    - with
-    - without
-
-RSpec/ExampleLength:
-  Max: 20
-
-RSpec/NestedGroups:
-  Enabled: false

data/Gemfile

@@ -1,27 +0,0 @@
-# frozen_string_literal: true
-
-source 'https://rubygems.org'
-
-# Specify your gem's dependencies in f_service.gemspec
-gemspec
-
-group :development, :test do
-  gem 'pry'
-  gem 'pry-nav'
-  gem 'rake', '~> 13.0.0'
-  gem 'rubocop', '~> 0.82.0', require: false
-  gem 'rubocop-rspec', require: false
-end
-
-group :docs do
-  gem 'yard'
-end
-
-group :optional do
-  gem 'solargraph'
-end
-
-group :test do
-  gem 'rspec', '~> 3.0'
-  gem 'simplecov', require: false
-end

data/Gemfile.lock

@@ -1,103 +0,0 @@
-PATH
-  remote: .
-  specs:
-    f_service (0.3.0)
-
-GEM
-  remote: https://rubygems.org/
-  specs:
-    ast (2.4.0)
-    backport (1.1.2)
-    benchmark (0.1.0)
-    coderay (1.1.3)
-    diff-lcs (1.3)
-    docile (1.3.5)
-    e2mmap (0.1.0)
-    jaro_winkler (1.5.4)
-    maruku (0.7.3)
-    method_source (1.0.0)
-    mini_portile2 (2.8.1)
-    nokogiri (1.14.3)
-      mini_portile2 (~> 2.8.0)
-      racc (~> 1.4)
-    parallel (1.19.1)
-    parser (2.7.1.1)
-      ast (~> 2.4.0)
-    pry (0.14.1)
-      coderay (~> 1.1)
-      method_source (~> 1.0)
-    pry-nav (1.0.0)
-      pry (>= 0.9.10, < 0.15)
-    racc (1.6.2)
-    rainbow (3.0.0)
-    rake (13.0.1)
-    reverse_markdown (1.4.0)
-      nokogiri
-    rexml (3.2.5)
-    rspec (3.9.0)
-      rspec-core (~> 3.9.0)
-      rspec-expectations (~> 3.9.0)
-      rspec-mocks (~> 3.9.0)
-    rspec-core (3.9.1)
-      rspec-support (~> 3.9.1)
-    rspec-expectations (3.9.1)
-      diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.9.0)
-    rspec-mocks (3.9.1)
-      diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.9.0)
-    rspec-support (3.9.2)
-    rubocop (0.82.0)
-      jaro_winkler (~> 1.5.1)
-      parallel (~> 1.10)
-      parser (>= 2.7.0.1)
-      rainbow (>= 2.2.2, < 4.0)
-      rexml
-      ruby-progressbar (~> 1.7)
-      unicode-display_width (>= 1.4.0, < 2.0)
-    rubocop-rspec (1.38.1)
-      rubocop (>= 0.68.1)
-    ruby-progressbar (1.10.1)
-    simplecov (0.21.2)
-      docile (~> 1.1)
-      simplecov-html (~> 0.11)
-      simplecov_json_formatter (~> 0.1)
-    simplecov-html (0.12.3)
-    simplecov_json_formatter (0.1.2)
-    solargraph (0.38.6)
-      backport (~> 1.1)
-      benchmark
-      bundler (>= 1.17.2)
-      e2mmap
-      jaro_winkler (~> 1.5)
-      maruku (~> 0.7, >= 0.7.3)
-      nokogiri (~> 1.9, >= 1.9.1)
-      parser (~> 2.3)
-      reverse_markdown (~> 1.0, >= 1.0.5)
-      rubocop (~> 0.52)
-      thor (~> 1.0)
-      tilt (~> 2.0)
-      yard (~> 0.9)
-    thor (1.0.1)
-    tilt (2.0.10)
-    unicode-display_width (1.7.0)
-    yard (0.9.24)
-
-PLATFORMS
-  ruby
-
-DEPENDENCIES
-  bundler (~> 2.0)
-  f_service!
-  pry
-  pry-nav
-  rake (~> 13.0.0)
-  rspec (~> 3.0)
-  rubocop (~> 0.82.0)
-  rubocop-rspec
-  simplecov
-  solargraph
-  yard
-
-BUNDLED WITH
-   2.2.32

data/Rakefile

@@ -1,11 +0,0 @@
-# frozen_string_literal: true
-
-require 'bundler/gem_tasks'
-require 'rspec/core/rake_task'
-require 'yard'
-
-RSpec::Core::RakeTask.new(:spec)
-
-task default: :spec
-
-YARD::Rake::YardocTask.new

data/bin/console

@@ -1,15 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-
-require 'bundler/setup'
-require 'f_service'
-
-# 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