multi_block 1.1 → 1.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: a5e8f01ab709dd3be84548791a9b7b67e43bd350
-  data.tar.gz: 2137ce5ca59fb9fbdcd9eefc303998e1bda61071
+SHA256:
+  metadata.gz: 4a6ff03fb7c3235d1d48b5fe5f64590fd6c8e74d2621d62aed2870e105a36904
+  data.tar.gz: 7131421a9ae98d9eb53b92220362435ebace0f177e3e1495f2d293f333b9cd42
 SHA512:
-  metadata.gz: 38d32e968578403ca6f2bdf1e0dfde082d589a4d0d755b4e0febed43c61deec346521f5af7ad66f4d1504a87ac603781b6affcfea8b2d430e27dffa3155892fe
-  data.tar.gz: 6b75186f120a1008aeb5ade1aafb374264d8e046d7e64fa905e937b261c516f9325ad00a75e9457b818e09cfbf122b9e636783c4b4fe463a7f03dc9e6a0bf9a9
+  metadata.gz: 9fb4375c0a9fb3a8d463836ea3f90aa6d3ed95cf43bf7f2ee378f3a8d7024b2355a6a376e4b2abbbca648cf208458b5ddfdaa385dc2210335f50464b3a21b8c4
+  data.tar.gz: e5da313ef554331df006502215bb6e0268d9c708b405d3eb5e1f7521dc916dd8fc86c573b1d03a535c5d58ab1b125e60389dc4443c86dbbfaca61dc40952bae9

data/{CHANGELOG.rdoc → CHANGELOG.md}

@@ -1,6 +1,15 @@
-== 1.1.0 (master)
+# Change Log
+
+## 1.2
+
+* Update project setup to 2021
+* Re-release
+
+## 1.1
+
 * Updates for 2015 Rubies, drop support for Ruby 1
 * Simplify activating Array extension via: require 'multi_block/array'
 
-== 1.0.0
+## 1.0
+
 * Initial Release

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# 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 conduct@janlelis.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]: https://contributor-covenant.org
+[version]: https://contributor-covenant.org/version/1/4/

data/{README.rdoc → README.md}

@@ -1,17 +1,18 @@
-= MultiBlock {<img src="https://badge.fury.io/rb/multi_block.svg" />}[http://badge.fury.io/rb/multi_block] {<img src="https://travis-ci.org/janlelis/multi_block.png" />}[https://travis-ci.org/janlelis/multi_block]
+# MultiBlock [<img src="https://badge.fury.io/rb/multi_block.svg" />](https://badge.fury.io/rb/multi_block) [<img src="https://github.com/janlelis/multi_block/workflows/Test/badge.svg" />](https://github.com/janlelis/multi_block/actions?query=workflow%3ATest)
 
-MultiBlock is a mini framework for passing multiple blocks to methods. It uses {named procs}[https://github.com/janlelis/named_proc] to accomplish this with a simple syntax. The receiving method can either yield all blocks, or just call specific ones, identified by order or name.
+MultiBlock is a mini framework for passing multiple blocks to methods. It uses [named procs](https://github.com/janlelis/named_proc) to accomplish this with a simple syntax. The receiving method can either yield all blocks, or just call specific ones, identified by order or name.
 
+Currently supports CRuby only.
 
-== Setup
+## Setup
 
 Add to Gemfile:
 
     gem 'multi_block'
 
 
-== Usage
-=== Defining methods that use multiple blocks
+## Usage
+### Defining methods that use multiple blocks
 
 The first argument given to yield always defines the desired block(s). The other arguments get directly passed to the block(s):
 
@@ -25,7 +26,7 @@ The first argument given to yield always defines the desired block(s). The other
           error:   [500, "Internal Brawl Error"]     #       values are the args
 
 
-=== Calling methods with multiple blocks
+### Calling methods with multiple blocks
 
 Consider these two example methods:
 
@@ -41,7 +42,7 @@ Consider these two example methods:
     end
 
 
-Multiple blocks can be passed using +blocks+:
+Multiple blocks can be passed using `blocks`:
 
     ajax &blocks[
       proc.success{ puts "Yeah!"    },
@@ -61,13 +62,13 @@ The dice method could, for example, be called in this way:
     ]
 
 
-== Bonus sugar: Array extension
+## Bonus sugar: Array extension
 
-If you like the slim <tt>&to_proc</tt> operator, you can further optimize the syntax by activating the core extension for array:
+If you like the slim `&to_proc` operator, you can further optimize the syntax by activating the core extension for array:
 
     require 'multi_block/array'
 
-Now you do not need the +blocks+ helper anymore. Instead just do:
+Now you do not need the `blocks` helper anymore. Instead just do:
 
     do_something, some_argument, &[
       proc.easy_way{
@@ -79,5 +80,6 @@ Now you do not need the +blocks+ helper anymore. Instead just do:
     ]
 
 
-== MIT License
+## MIT License
+
 See the original gist: https://gist.github.com/4b2f5fd0b45118e46d0f

data/lib/multi_block/version.rb

@@ -1,3 +1,5 @@
+# frozen_string_literal: true
+
 module MultiBlock
-  VERSION = "1.1".freeze
+  VERSION = "1.2"
 end

data/multi_block.gemspec

@@ -6,15 +6,15 @@ Gem::Specification.new do |s|
   s.name        = "multi_block"
   s.version     = MultiBlock::VERSION
   s.authors     = ["Jan Lelis"]
-  s.email       = "mail@janlelis.de"
+  s.email       = "hi@ruby.consulting"
   s.homepage    = "https://github.com/janlelis/multi_block"
   s.summary     = 'MultiBlock is a mini framework for passing multiple blocks to methods.'
   s.description = 'MultiBlock is a mini framework for passing multiple blocks to methods. It uses "named procs" to accomplish this in a nice way. The receiving method can either yield all blocks, or just call specific ones, identified by order or name. '
   s.required_ruby_version = '>= 1.9.3'
   s.files = Dir.glob %w{multi_block.gemspec lib/multi_block.rb lib/multi_block/version.rb lib/multi_block/implementation.rb lib/multi_block/core_ext.rb lib/multi_block/array.rb spec/multi_block_spec.rb}
-  s.extra_rdoc_files = ["README.rdoc", "MIT-LICENSE.txt", "CHANGELOG.rdoc", ".travis.yml"]
+  s.extra_rdoc_files = ["README.md", "MIT-LICENSE.txt", "CHANGELOG.md", "CODE_OF_CONDUCT.md"]
   s.license = 'MIT'
-  s.add_dependency 'named_proc', '~> 1.1'
+  s.add_dependency 'named_proc', '~> 1.2'
   s.add_development_dependency 'rspec', '~> 3.2'
-  s.add_development_dependency 'rake', '~> 10.4'
+  s.add_development_dependency 'rake', '~> 13.0'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: multi_block
 version: !ruby/object:Gem::Version
-  version: '1.1'
+  version: '1.2'
 platform: ruby
 authors:
 - Jan Lelis
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-03-20 00:00:00.000000000 Z
+date: 2021-11-18 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: named_proc
@@ -16,14 +16,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.1'
+        version: '1.2'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.1'
+        version: '1.2'
 - !ruby/object:Gem::Dependency
   name: rspec
   requirement: !ruby/object:Gem::Requirement
@@ -44,30 +44,30 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '10.4'
+        version: '13.0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '10.4'
+        version: '13.0'
 description: 'MultiBlock is a mini framework for passing multiple blocks to methods.
   It uses "named procs" to accomplish this in a nice way. The receiving method can
   either yield all blocks, or just call specific ones, identified by order or name. '
-email: mail@janlelis.de
+email: hi@ruby.consulting
 executables: []
 extensions: []
 extra_rdoc_files:
-- README.rdoc
+- README.md
 - MIT-LICENSE.txt
-- CHANGELOG.rdoc
-- ".travis.yml"
+- CHANGELOG.md
+- CODE_OF_CONDUCT.md
 files:
-- ".travis.yml"
-- CHANGELOG.rdoc
+- CHANGELOG.md
+- CODE_OF_CONDUCT.md
 - MIT-LICENSE.txt
-- README.rdoc
+- README.md
 - lib/multi_block.rb
 - lib/multi_block/array.rb
 - lib/multi_block/core_ext.rb
@@ -94,8 +94,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubyforge_project: 
-rubygems_version: 2.4.6
+rubygems_version: 3.2.22
 signing_key: 
 specification_version: 4
 summary: MultiBlock is a mini framework for passing multiple blocks to methods.

data/.travis.yml

@@ -1,17 +0,0 @@
-language: ruby
-
-rvm:
-- ruby-head
-- 2.2.1
-- 2.2.0
-- 2.1.5
-- 2.1.4
-- 2.1.3
-- 2.1.2
-- 2.1.1
-- 2.1.0
-- 2.0.0
-- rbx-2
-- jruby-head
-- jruby-9000
-