dry-monads 1.3.5 → 1.4.0

data/docsite/source/unit.html.md

@@ -1,36 +0,0 @@
----
-title: Unit
-layout: gem-single
-name: dry-monads
----
-
-Some constructors do not require you to pass a value. As a default they use `Unit`, a special singleton value:
-
-```ruby
-extend Dry::Monads[:result]
-
-Success().value! # => Unit
-```
-
-`Unit` doesn't have any special properties or methods, it's similar to `nil` except for it is not i.e. `if Unit` passes.
-
-`Unit` is usually excluded from the output:
-
-```ruby
-extend Dry::Monads[:result]
-
-# Outputs as "Success()" but technically it's "Success(Unit)"
-Success()
-```
-
-### Discarding values
-
-When the outcome of an operation is not a caller's concern, call `.discard`, it will map the wrapped value to `Unit`:
-
-```ruby
-extend Dry::Monads[:result]
-
-result = create_user # returns Success(#<User...>) or Failure(...)
-
-result.discard # => Maps Success(#<User ...>) to Success() but lefts Failure(...) intact
-```

data/docsite/source/validated.html.md

@@ -1,88 +0,0 @@
----
-title: Validated
-layout: gem-single
-name: dry-monads
----
-
-Suppose you've got a form to validate. If you are using `Result` combined with `Do` your code might look like this:
-
-```ruby
-require 'dry/monads'
-
-class CreateAccount
-  include Dry::Monads[:result, :do]
-
-  def call(form)
-    name = yield validate_name(form)
-    email = yield validate_email(form)
-    password = yield validate_password(form)
-
-    user = repo.create_user(
-      name: name,
-      email: email,
-      password: password
-    )
-
-    Success(user)
-  end
-
-  def validate_name(form)
-    # Success(name) or Failure(:invalid_name)
-  end
-
-  def validate_email(form)
-    # Success(email) or Failure(:invalid_email)
-  end
-
-  def validate_password(form)
-    # Success(password) or Failure(:invalid_password)
-  end
-end
-```
-
-If any of the validation steps fails the user will see an error. The problem is if `name` is not valid the user won't see errors about invalid `email` and `password`, if any. `Validated` circumvents this particular problem.
-
-`Validated` is actually not a monad but an applicative functor. This means you can't call `bind` on it. Instead, it can accumulate values in combination with `List`:
-
-```ruby
-require 'dry/monads'
-
-class CreateAccount
-  include Dry::Monads[:list, :result, :validated, :do]
-
-  def call(form)
-    name, email, password = yield List::Validated[
-      validate_name(form),
-      validate_email(form),
-      validate_password(form)
-    ].traverse.to_result
-
-    user = repo.create_user(
-      name: name,
-      email: email,
-      password: password
-    )
-
-    Success(user)
-  end
-
-  def validate_name(form)
-    # Valid(name) or Invalid(:invalid_name)
-  end
-
-  def validate_email(form)
-    # Valid(email) or Invalid(:invalid_email)
-  end
-
-  def validate_password(form)
-    # Valid(password) or Invalid(:invalid_password)
-  end
-end
-```
-
-Here all validations will be processed at once, if any of them fails the result will be converted to a `Failure` wrapping the `List` of errors:
-
-```ruby
-create_account.(form)
-# => Failure(List[:invalid_name, :invalid_email])
-```

data/project.yml

@@ -1,2 +0,0 @@
-name: dry-monads
-codacy_id: f2eed41bf7f04b38b0a7691c2cf6e73c