named_proc 1.1 → 1.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: cbf28423889dfba4dbbdcb64f38cd3c83dfb9922
-  data.tar.gz: 52119a8217037574c2e8fc755e57d9655737306c
+SHA256:
+  metadata.gz: d56ef525a2ccfe33b27b5d130bb66e2aa2aeda4b8510c3b0e0f95b6cf102dcba
+  data.tar.gz: c49198ce58c0703f69f9f17edc1b569bcc10426631408d8b088c70715c459537
 SHA512:
-  metadata.gz: e303b748dbd73e992f7bbc54ce167abaeb9805cca83fa0f7ecb0c25f83312e9d6ac84b8835fb8b5b3f23627ce9f121b541586f0e4d4b8dd3cd60a52b3250645f
-  data.tar.gz: 346258671dd9f5ceac348d2271e20b2f9fcf0f3cbd64a33f8e9edec7b729f82bfe9a1b64ad3bf695d55f17e58917c3155e4d4e3f6fdb31742d1f27b805fb9229
+  metadata.gz: 42d1afa38c1c0b5128fc72e08957a689f214ed8c28f0369e6f3486b6300b50e2ee009bfbfc8ab8c2ecfa72e7ff5e21486008ab841db819fab99b230a62966e22
+  data.tar.gz: aaf9a8e4eb90f881a6e94eb9dfa22c9c3fe87757b97fb416d9be81c5e7b1a5554e86425d68e6503dad69ebf0d2e6a8bfb4cc22d5f8154f23e95c769059680387

data/{CHANGELOG.rdoc → CHANGELOG.md}

@@ -1,7 +1,16 @@
-== 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
 * Fix method to lambdafy a proc
 * Add proc name to NamedProc#inspect
 
-== 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,18 +1,19 @@
-= Named Proc {<img src="https://badge.fury.io/rb/named_proc.svg" />}[http://badge.fury.io/rb/named_proc] {<img src="https://travis-ci.org/janlelis/named_proc.png" />}[https://travis-ci.org/janlelis/named_proc]
+# Named Proc [<img src="https://badge.fury.io/rb/named_proc.svg" />](https://badge.fury.io/rb/named_proc) [<img src="https://github.com/janlelis/named_proc/workflows/Test/badge.svg" />](https://github.com/janlelis/named_proc/actions?query=workflow%3ATest)
 
-When working with a lot of procs, naming them might become handy. It makes identifying them later easier, which can be utilized by your code. For example, it enables improves the usefulness of {multi_block}[https:/github.com/janlelis/multi_block], a gem that allows you to pass multiple procs to methods.
+When working with a lot of procs, naming them might become handy. It makes identifying them later easier. For an example that uses named procs, see the [multi_block](https://github.com/janlelis/multi_block) gem!
 
+Currently supports CRuby only.
 
-== Setup
+## Setup
 
 Add to Gemfile:
 
     gem 'named_proc'
 
 
-== Named Procs
+## Named Procs
 
-A named proc acts like a normal proc, but it has a name attribute. You create it by calling a method with the desired name on +proc+:
+A named proc acts like a normal proc, but it has a name attribute. You create it by calling a method with the desired name on `proc`:
 
     >> a = proc.even?{ |e| e.even? }
     => #<NamedProc:0x00000001ffc340@(irb):1>
@@ -32,5 +33,6 @@ In the same way, you can create lambdas:
     >> b.lambda?
     => true
 
-== MIT License
+## MIT License
+
 The original gist: https://gist.github.com/4b2f5fd0b45118e46d0f

data/lib/named_proc/version.rb

@@ -1,3 +1,5 @@
+# frozen_string_literal: true
+
 class NamedProc < Proc
-  VERSION = "1.1".freeze
+  VERSION = "1.2"
 end

data/named_proc.gemspec

@@ -6,14 +6,14 @@ Gem::Specification.new do |s|
   s.name        = "named_proc"
   s.version     = NamedProc::VERSION
   s.authors     = ["Jan Lelis"]
-  s.email       = "mail@janlelis.de"
+  s.email       = "hi@ruby.consulting"
   s.homepage    = "https://github.com/janlelis/named_proc"
   s.summary     = "NamedProc: Like anonymous procs, but have a name."
   s.description = "NamedProc: Like anonymous procs, but have a name. Example: lambda.codebrawl {} # creates an empty lambda with the name :codebrawl"
   s.files = Dir.glob %w{named_proc.gemspec lib/named_proc.rb lib/named_proc/version.rb lib/named_proc/implementation.rb lib/named_proc/core_ext.rb spec/named_proc_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.required_ruby_version = '>= 1.9.3'
   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: named_proc
 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: rspec
@@ -30,29 +30,29 @@ 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: 'NamedProc: Like anonymous procs, but have a name. Example: lambda.codebrawl
   {} # creates an empty lambda with the name :codebrawl'
-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/named_proc.rb
 - lib/named_proc/core_ext.rb
 - lib/named_proc/implementation.rb
@@ -78,8 +78,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: 'NamedProc: Like anonymous procs, but have a name.'

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
-