web_pipe 0.14.0 → 0.15.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 248232882dde49a235e15080f2c9c2abb1188e29e10f228f43d0c30c6c5f116f
-  data.tar.gz: ad6afa0399cdb99d80ef46fb1bcdde037e987e8fe01756f2c667301a9f622d5e
+  metadata.gz: 8a8ebc7025774af2e5938efb5c76a0ff120bc386f449900781e3f05d35eb6a15
+  data.tar.gz: a6e03d72fb7cb3bd384cea1f51369f21a375b4a009b8409ef3a588600adc07b7
 SHA512:
-  metadata.gz: 399f912c144ac66bd1bfeaf58708a8e52ed7e296f5e592c9f9422fd3fd6553a4e3c16c0fec2986cf4fd278857d5acd1078d7b1a7e9e0e07ad9f18824303953ba
-  data.tar.gz: 41c539bee15aa9d3f8ae23bc88cd02ba5dc113ad9245290c330a269917716d12da5637852153d2f9bd7b324e8101f2a1329b267e5ebc409ae0c5cb419cd932f8
+  metadata.gz: 278d8402ec4ea79266eefd3ee558522af3923bb23232b3fcefd8574d73dc64c8106757f910a1c312ceed57889ee352e5955c19641601dfdcb47bcbbc63673bb8
+  data.tar.gz: 99ae42906946fbdda913bbf4f0cdd2cc1a6c3951ffb5972b52bb11b5caf882b6b6c286b68aca9d92ce0e6974d6168178860ae164d3d49af7bcb36556202b70dc

data/CHANGELOG.md

@@ -4,6 +4,11 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](http://keepachangelog.com/)
 and this project adheres to [Semantic Versioning](http://semver.org/).
 
+## [0.15.0] - 2021-09-12
+- **BREAKING**. Switch `dry_view` extension with `hanami_view`.
+  [#45](https://github.com/waiting-for-dev/web_pipe/pull/45)
+
+### Added
 ## [0.14.0] - 2021-04-14
 ### Added
 - Inspecting operations

data/Gemfile

@@ -7,7 +7,7 @@ git_source(:github) { |repo_name| "https://github.com/#{repo_name}" }
 # Specify your gem's dependencies in web_pipe.gemspec
 gemspec
 
-# TODO: Remove when dry-rb 0.8 is released (ruby 3.0 support)
 group :development do
-  gem 'dry-view', github: 'dry-rb/dry-view', ref: 'a048e32'
+  # TODO: Move to gemspec when hanami-view 2.0 is available
+  gem 'hanami-view', github: 'hanami/view', tag: 'v2.0.0.alpha2'
 end

data/README.md

@@ -40,7 +40,7 @@ extension](docs/extensions/rails.md).
    1. [Cookies](docs/extensions/cookies.md)
    1. [Flash](docs/extensions/flash.md)
    1. [Dry Schema](docs/extensions/dry_schema.md)
-   1. [Dry View](docs/extensions/dry_view.md)
+   1. [Hanami View](docs/extensions/hanami_view.md)
    1. [Params](docs/extensions/params.md)
    1. [Rails](docs/extensions/rails.md)
    1. [Redirect](docs/extensions/redirect.md)

data/docs/extensions/{dry_view.md → hanami_view.md}

@@ -1,8 +1,10 @@
-# Dry View
+# Hanami View
 
-This extensions integrates with
-[dry-view](https://dry-rb.org/gems/dry-view/) rendering system to
-set a dry-view output as response body.
+> This extension currently works with `hanami-view` v2.0.0.alpha2, which is not
+still released but it's available on the gem repository.
+
+This extensions integrates with [hanami-view](https://github.com/hanami/view)
+rendering system to set a hanami-view output as response body.
 
 `WebPipe::Conn#view` method is at the core of this extension. In its basic
 behaviour, you provide to it a view instance you want to render and any
@@ -10,12 +12,12 @@ exposures or options it may need:
 
 ```ruby
 require 'web_pipe'
-require 'dry/view'
+require 'hanami/view'
 require 'my_context'
 
-WebPipe.load_extensions(:dry_view)
+WebPipe.load_extensions(:hanami_view)
 
-class SayHelloView < Dry::View
+class SayHelloView < Hanami::View
   config.paths = [File.join(__dir__, '..', 'templates')]
   config.template = 'say_hello'
   config.default_context = MyContext
@@ -40,12 +42,12 @@ However, you can resolve a view from a container if you also use (`:container`
 extension)[container.md]:
 
 ```ruby
-require 'dry_view'
+require 'hanami_view'
 require 'my_container'
 require 'web_pipe'
 require 'web_pipe/plugs/config'
 
-WebPipe.load_extensions(:dry_view, :container)
+WebPipe.load_extensions(:hanami_view, :container)
 
 class MyApp
  include WebPipe
@@ -61,20 +63,20 @@ class MyApp
 end
 ```
 
-As in a standard call to `Dry::View#call`, you can override the context
-(`Dry::View::Context`) to use through `context:` option. However, it is still
+As in a standard call to `Hanami::View#call`, you can override the context
+(`Hanami::View::Context`) to use through `context:` option. However, it is still
 possible to leverage configured default context while being able to inject
 request specific data to it.
 
 For that to work, you have to specify required dependencies (in this case,
-request specific data) to your dry-view's context. A very convenient way to do
+request specific data) to your hanami-view's context. A very convenient way to do
 that is with [`dry-auto_inject`](https://dry-rb.org/gems/dry-auto_inject):
 
 ```ruby
-require 'dry/view/context'
+require 'hanami/view/context'
 require 'my_import'
 
-class MyContext < Dry::View::Context
+class MyContext < Hanami::View::Context
  include MyImport::Import[:current_path]
  
  # Without `dry-auto_inject` you have to manually specify dependencies and

data/docs/extensions/rails.md

@@ -31,10 +31,9 @@ It's quite possible that you don't need more than that in terms of rails
 integration. Of course, surely you want something more elaborate to generate
 responses. For that, you can use the view or template system you like. One
 option that will play specially well here is
-[`dry-view`](https://dry-rb.org/gems/dry-view/), which
-[integrates](https://github.com/dry-rb/dry-view/tree/master/examples/rails)
-itself easily with Rails. Furthermore, we have a tailored `dry_view`
-[extension](https://waiting-for-dev.github.io/web_pipe/docs/extensions/dry_view.html).
+[`hanami-view`](https://github.com/hanami/view). Furthermore, we have a
+tailored `hanami_view`
+[extension](https://waiting-for-dev.github.io/web_pipe/docs/extensions/hanami_view.html).
 
 You need to use `:rails` extension if:
 

data/docs/recipes/dry_rb_integration.md

@@ -3,9 +3,8 @@
 `web_pipe` has been designed to integrate smoothly with
 [dry-rb](https://dry-rb.org/) ecosystem. It shares same design
 principles and it ships with some extensions which even make this
-integration tighter (like
-[`:dry-view`](../extensions/dry_view.md) or
-[`:dry-schema`](../extensions/dry_schema.md) extensions).
+integration tighter (like [`:dry-schema`](../extensions/dry_schema.md)
+extension).
 
 If you want to use `web_pipe` with the rest of dry-rb libraries,
 your best bet is to use

data/lib/web_pipe/extensions/{dry_view/dry_view.rb → hanami_view/hanami_view.rb}

@@ -2,19 +2,19 @@
 
 require 'web_pipe/types'
 require 'web_pipe/conn'
-require 'dry/view'
+require 'hanami/view'
 
 #:nodoc:
 module WebPipe
-  # Integration with `dry-view` rendering system.
+  # Integration with `hanami-view` rendering system.
   #
   # This extensions adds a {#view} method to {WebPipe::Conn} which
-  # sets the string output of a `dry-view` view as response body.
+  # sets the string output of a `hanami-view` view as response body.
   #
   # @example
-  #   WebPipe.load_extensions(:dry_view)
+  #   WebPipe.load_extensions(:hanami_view)
   #
-  #   class SayHelloView < Dry::View
+  #   class SayHelloView < Hanami::View
   #     config.paths = [File.join(__dir__, '..', 'templates')]
   #     config.template = 'say_hello'
   #
@@ -35,7 +35,7 @@ module WebPipe
   # instance can be resolved from it.
   #
   # @example
-  #   WebPipe.load_extensions(:dry_view, :container)
+  #   WebPipe.load_extensions(:hanami_view, :container)
   #
   #   class App
   #     include WebPipe
@@ -50,18 +50,18 @@ module WebPipe
   #     end
   #  end
   #
-  # Context ({Dry::View::Context}) for the view can be set explicetly
+  # Context ({Hanami::View::Context}) for the view can be set explicetly
   # through the `context:` argument, as in a standard call to
-  # {Dry::View#call}. However, it is possible to leverage configured
+  # {Hanami::View#call}. However, it is possible to leverage configured
   # default context while still being able to inject request specific
   # context. For that to work, `:view_context` should be present in
   # {WebPipe::Conn#config}. Its value must be a lambda accepting the
   # {Conn} instance and returning a hash, which will be passed to
-  # {Dry::View::Context#with} to create the final context at the
+  # {Hanami::View::Context#with} to create the final context at the
   # moment {#view} is called.
   #
   # @example
-  #   class MyContext < Dry::View::Context
+  #   class MyContext < Hanami::View::Context
   #     attr_reader :current_path
   #
   #     def initialize(current_path: nil, **options)
@@ -70,7 +70,7 @@ module WebPipe
   #     end
   #   end
   #
-  #   class SayHelloView < Dry::View
+  #   class SayHelloView < Hanami::View
   #     config.paths = [File.join(__dir__, '..', 'templates')]
   #     config.template = 'say_hello'
   #     config.default_context = MyContext.new
@@ -96,7 +96,7 @@ module WebPipe
   #     end
   #   end
   #
-  # @see https://dry-rb.org/gems/dry-view/
+  # @see https://github.com/hanami/view
   # @see WebPipe::Container
   module DryView
     # Where to find in {#config} request's view context generator.
@@ -107,17 +107,17 @@ module WebPipe
 
     # Sets string output of a view as response body.
     #
-    # If the view is not a {Dry::View} instance, it is resolved from
+    # If the view is not a {Hanami::View} instance, it is resolved from
     # the configured container.
     #
     # `kwargs` is used as the input for the view (the arguments that
-    # {Dry::View#call} receives). If they doesn't contain an explicit
+    # {Hanami::View#call} receives). If they doesn't contain an explicit
     # `context:` key, it can be added through the injection of the
     # result of a lambda present in context's `:view_context`.(see
-    # {Dry::View::Context#with}).
+    # {Hanami::View::Context#with}).
     #
-    # @param view_spec [Dry::View, Any]
-    # @param kwargs [Hash] Arguments to pass along to `Dry::View#call`
+    # @param view_spec [Hanami::View, Any]
+    # @param kwargs [Hash] Arguments to pass along to `Hanami::View#call`
     #
     # @return WebPipe::Conn
     def view(view_spec, **kwargs)
@@ -134,7 +134,7 @@ module WebPipe
     private
 
     def view_instance(view_spec)
-      return view_spec if view_spec.is_a?(Dry::View)
+      return view_spec if view_spec.is_a?(Hanami::View)
 
       fetch_config(:container)[view_spec]
     end

data/lib/web_pipe/extensions/rails/rails.rb

@@ -37,9 +37,8 @@ module WebPipe
   # It's quite possible that you don't need more than that in terms of rails
   # integration. Of course, surely you want something more elaborate to generate
   # responses. For that, you can use the view or template system you like. One
-  # option that will play specially well here is `dry-view`, which integrates
-  # itself easily with Rails. Furthermore, we have a tailored `dry_view`
-  # extension.
+  # option that will play specially well here is `hanami-view`. Furthermore, we
+  # have a tailored `hanami_view` extension.
   #
   # You need to use `:rails` extension if:
   #
@@ -118,9 +117,6 @@ module WebPipe
   # https://github.com/waiting-for-dev/rails-web_pipe
   #
   # @see https://guides.rubyonrails.org/routing.html#routing-to-rack-applications
-  # @see https://dry-rb.org/gems/dry-view/
-  # @see https://github.com/dry-rb/dry-view/tree/master/examples/rails
-  # @see https://waiting-for-dev.github.io/web_pipe/docs/extensions/dry_view.html
   # @see https://api.rubyonrails.org/v6.0.1/classes/ActionController/Renderer.html
   # @see https://api.rubyonrails.org/v6.0.1/classes/ActionController/Renderer.html
   # @see https://api.rubyonrails.org/v6.0.1/classes/ActionView/Helpers/UrlHelper.html

data/lib/web_pipe/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module WebPipe
-  VERSION = '0.14.0'
+  VERSION = '0.15.0'
 end

data/lib/web_pipe.rb

@@ -27,8 +27,8 @@ module WebPipe
     require 'web_pipe/extensions/dry_schema/plugs/sanitize_params'
   end
 
-  register_extension :dry_view do
-    require 'web_pipe/extensions/dry_view/dry_view'
+  register_extension :hanami_view do
+    require 'web_pipe/extensions/hanami_view/hanami_view'
   end
 
   register_extension :container do

data/web_pipe.gemspec

@@ -43,8 +43,6 @@ Gem::Specification.new do |spec|
   spec.add_development_dependency 'bundler'
   spec.add_development_dependency 'dry-schema', '~> 1.0'
   spec.add_development_dependency 'dry-transformer', '~> 0.1'
-  # TODO: Readd when dry-rb 0.8 is released (ruby 3.0 support)
-  # spec.add_development_dependency 'dry-view', '~> 0.8'
   spec.add_development_dependency 'pry-byebug'
   spec.add_development_dependency 'rack-flash3', '~> 1.0'
   spec.add_development_dependency 'rack-test', '~> 1.1'

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: web_pipe
 version: !ruby/object:Gem::Version
-  version: 0.14.0
+  version: 0.15.0
 platform: ruby
 authors:
 - Marc Busqué
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2021-04-14 00:00:00.000000000 Z
+date: 2021-09-12 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: dry-monads
@@ -277,8 +277,8 @@ files:
 - docs/extensions/container.md
 - docs/extensions/cookies.md
 - docs/extensions/dry_schema.md
-- docs/extensions/dry_view.md
 - docs/extensions/flash.md
+- docs/extensions/hanami_view.md
 - docs/extensions/params.md
 - docs/extensions/rails.md
 - docs/extensions/redirect.md
@@ -318,8 +318,8 @@ files:
 - lib/web_pipe/extensions/cookies/cookies.rb
 - lib/web_pipe/extensions/dry_schema/dry_schema.rb
 - lib/web_pipe/extensions/dry_schema/plugs/sanitize_params.rb
-- lib/web_pipe/extensions/dry_view/dry_view.rb
 - lib/web_pipe/extensions/flash/flash.rb
+- lib/web_pipe/extensions/hanami_view/hanami_view.rb
 - lib/web_pipe/extensions/params/params.rb
 - lib/web_pipe/extensions/params/params/transf.rb
 - lib/web_pipe/extensions/rails/rails.rb