reality-mash 1.0.0 → 1.1.0

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
- SHA1:
3
- metadata.gz: 138f9fd70723fc4bbb52792a604386c51e30ac32
4
- data.tar.gz: 504916813b92bef113248e47a82c27feca50233b
2
+ SHA256:
3
+ metadata.gz: 3632488bad7225a310ba9bd2936c656cb1f9919bd28a1ce2bcb49e22f48d764f
4
+ data.tar.gz: 767028987782d17c7872158823b51b8fea74e2c7520ecf7b16da9f0b7d4ab623
5
5
  SHA512:
6
- metadata.gz: 6149f7ae1acb73cf84d473028d6d04ec24fbd2751a5470bf7c50bf99448ee648783056abd99109efc3b9f3edc36bb22eab6abf6d1f5902baf5220e3e86a7a8e9
7
- data.tar.gz: 5c67c503d9de7391304d4eb1aaf5645f14f0cd729a8cfe941cfd6e541444536fd08e7a7304f02959de4491d573bc8038f40892ef21d7e8623260d488cc2e2ae2
6
+ metadata.gz: 0e4163fce23d808f1284c3259e6e3cb1e0e18c9d5a56975f87aff570eea57f270a2c32e921a2605a54c378a66394e94a1cc9648a88575f284446ee00291f7166
7
+ data.tar.gz: 1bc73fa928e5ea0d8eddaef5b05326c85012636e1bebde86b137b8855d2f0f16cf80fa8542c8b045b87c6ad1246942735b0cc3f34c002c61a47e89a4db1ffa43
data/.gitattributes CHANGED
@@ -1,6 +1,12 @@
1
+ # DO NOT EDIT: File is auto-generated
1
2
  * -text
2
- *.rb text -crlf -binary
3
- *.rdoc text -crlf -binary
4
- *.textile text -crlf -binary
5
- *.txt text -crlf -binary
6
- *.erb text -crlf -binary
3
+ *.gemspec text
4
+ *.md text
5
+ *.rb text
6
+ *.yml text
7
+ .gitattributes text
8
+ .gitignore text
9
+ .ruby-version text
10
+ Gemfile text
11
+ LICENSE text
12
+ Rakefile text
@@ -0,0 +1,47 @@
1
+ <!--
2
+ Thanks for your interest in the project. I appreciate bugs filed and PRs submitted!
3
+ Please make sure that you are familiar with and follow the Code of Conduct for
4
+ this project (found in the CODE_OF_CONDUCT.md file).
5
+
6
+ Please fill out this template with all the relevant information so we can
7
+ understand what's going on and fix the issue.
8
+
9
+ I may ask you to submit the fix (after giving some direction).
10
+ -->
11
+
12
+ Environment:
13
+
14
+ <!--
15
+ Please provide the version of this project where the issue occurred as well as the
16
+ versions of other environmental factors. This could be virtual machine version, os
17
+ version, browser version etc.
18
+ -->
19
+
20
+ Relevant code or config:
21
+
22
+ ```
23
+
24
+ ```
25
+
26
+ What you did:
27
+
28
+
29
+
30
+ What happened:
31
+
32
+ <!-- Please provide the full error message/screenshots/anything -->
33
+
34
+ Reproduction repository:
35
+
36
+ <!--
37
+ If possible, please create a repository that reproduces the issue with the
38
+ minimal amount of code possible. It is highly recommended you take the time
39
+ to read "How to create a Minimal, Complete, and Verifiable example" at
40
+ https://stackoverflow.com/help/mcve
41
+ -->
42
+
43
+ Problem description:
44
+
45
+
46
+
47
+ Suggested solution:
data/.ruby-version CHANGED
@@ -1 +1 @@
1
- 2.3.1
1
+ 2.6.6
data/.travis.yml CHANGED
@@ -1,10 +1,11 @@
1
+ # Lock down dist to ensure that builds run on a distribution that supports oraclejdk8
2
+ dist: trusty
1
3
  language: ruby
2
- sudo: false
3
4
  rvm:
4
5
  - 2.3.1
5
6
  - jruby-19mode
6
7
  jdk:
7
- - oraclejdk7
8
+ - oraclejdk8
8
9
  git:
9
10
  depth: 10
10
11
  before_install:
@@ -0,0 +1,73 @@
1
+ # Contributor Covenant Code of Conduct
2
+
3
+ ## Our Pledge
4
+
5
+ In the interest of fostering an open and welcoming environment, we as
6
+ contributors and maintainers pledge to making participation in our project and
7
+ our community a harassment-free experience for everyone, regardless of age, body
8
+ size, disability, ethnicity, gender identity and expression, level of experience,
9
+ education, socio-economic status, nationality, personal appearance, race,
10
+ religion, or sexual identity and orientation.
11
+
12
+ ## Our Standards
13
+
14
+ Examples of behavior that contributes to creating a positive environment
15
+ include:
16
+
17
+ * Using welcoming and inclusive language
18
+ * Being respectful of differing viewpoints and experiences
19
+ * Gracefully accepting constructive criticism
20
+ * Focusing on what is best for the community
21
+ * Showing empathy towards other community members
22
+
23
+ Examples of unacceptable behavior by participants include:
24
+
25
+ * The use of sexualized language or imagery and unwelcome sexual attention or
26
+ advances
27
+ * Trolling, insulting/derogatory comments, and personal or political attacks
28
+ * Public or private harassment
29
+ * Publishing others' private information, such as a physical or electronic
30
+ address, without explicit permission
31
+ * Other conduct which could reasonably be considered inappropriate in a
32
+ professional setting
33
+
34
+ ## Our Responsibilities
35
+
36
+ Project maintainers are responsible for clarifying the standards of acceptable
37
+ behavior and are expected to take appropriate and fair corrective action in
38
+ response to any instances of unacceptable behavior.
39
+
40
+ Project maintainers have the right and responsibility to remove, edit, or
41
+ reject comments, commits, code, wiki edits, issues, and other contributions
42
+ that are not aligned to this Code of Conduct, or to ban temporarily or
43
+ permanently any contributor for other behaviors that they deem inappropriate,
44
+ threatening, offensive, or harmful.
45
+
46
+ ## Scope
47
+
48
+ This Code of Conduct applies both within project spaces and in public spaces
49
+ when an individual is representing the project or its community. Examples of
50
+ representing a project or community include using an official project e-mail
51
+ address, posting via an official social media account, or acting as an appointed
52
+ representative at an online or offline event. Representation of a project may be
53
+ further defined and clarified by project maintainers.
54
+
55
+ ## Enforcement
56
+
57
+ Instances of abusive, harassing, or otherwise unacceptable behavior may be
58
+ reported by contacting the project team at peter@realityforge.org. All
59
+ complaints will be reviewed and investigated and will result in a response that
60
+ is deemed necessary and appropriate to the circumstances. The project team is
61
+ obligated to maintain confidentiality with regard to the reporter of an incident.
62
+ Further details of specific enforcement policies may be posted separately.
63
+
64
+ Project maintainers who do not follow or enforce the Code of Conduct in good
65
+ faith may face temporary or permanent repercussions as determined by other
66
+ members of the project's leadership.
67
+
68
+ ## Attribution
69
+
70
+ This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71
+ available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
72
+
73
+ [homepage]: https://www.contributor-covenant.org
data/CONTRIBUTING.md CHANGED
@@ -1,19 +1,34 @@
1
1
  # How to Contribute
2
2
 
3
- Pull requests are greatly appreciated and are what makes opensource great. Here's a quick guide:
3
+ We'd love to accept your patches and contributions to this project. Pull requests are part of
4
+ what makes open source great. There are just a few small guidelines you need to follow.
4
5
 
5
- * Fork it
6
- * Create your feature branch (`git checkout -b my-new-feature`)
7
- * Commit your changes (`git commit -am 'Add some feature'`)
8
- * Push to the branch (`git push origin my-new-feature`)
9
- * Create new Pull Request
6
+ ## Code of Conduct
10
7
 
11
- Pester us if we don't get your Pull Requests merged in a timely fashion. :)
8
+ Participation in this project comes under the [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md)
9
+
10
+ ## Submitting code via Pull Requests
11
+
12
+ - We follow the [Github Pull Request Model](https://help.github.com/articles/about-pull-requests/) for
13
+ all contributions.
14
+ - For large bodies of work, we recommend creating an issue outlining the feature that you wish to build,
15
+ and describing how it will be implemented. This gives a chance for review to happen early, and ensures
16
+ no wasted effort occurs.
17
+ - All submissions, will require review before being merged.
18
+ - Finally - *Thanks* for considering submitting code to the project!
19
+
20
+ ## Formatting
21
+
22
+ When submitting pull requests, make sure to do the following:
23
+
24
+ - Maintain the same code style as the rest of the project.
25
+ - Remove trailing whitespace. Many editors will do this automatically.
26
+ - Ensure any new files have [a trailing newline](https://stackoverflow.com/questions/5813311/no-newline-at-end-of-file)
12
27
 
13
28
  ## How to speed the merging of pull requests
14
29
 
15
- * Describe your changes in the CHANGELOG.
16
- * Give yourself some credit in the appropriate place (usually the CHANGELOG).
30
+ * Describe your changes in the CHANGELOG.md (if present).
31
+ * Give yourself some credit in the appropriate place (usually the CHANGELOG.md).
17
32
  * Make commits of logical units.
18
33
  * Ensure your commit messages help others understand what you are doing and why.
19
34
  * Check for unnecessary whitespace with `git diff --check` before committing.
@@ -23,4 +38,6 @@ Pester us if we don't get your Pull Requests merged in a timely fashion. :)
23
38
  ## Additional Resources
24
39
 
25
40
  * [General GitHub documentation](http://help.github.com/)
26
- * [GitHub pull request documentation](http://help.github.com/send-pull-requests/)
41
+ * [How to write a good Git Commit message](https://chris.beams.io/posts/git-commit/) -
42
+ Great way to make sure your Pull Requests get accepted.
43
+ * [An Open Source Etiquette Guidebook](https://css-tricks.com/open-source-etiquette-guidebook/#article-header-id-1)
data/README.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # reality-mash
2
2
 
3
- [![Build Status](https://secure.travis-ci.org/realityforge/reality-mash.png?branch=master)](http://travis-ci.org/realityforge/reality-mash)
3
+ [![Build Status](https://api.travis-ci.com/realityforge/reality-mash.svg?branch=master)](http://travis-ci.com/realityforge/reality-mash)
4
4
 
5
5
  `reality-mash` is a simple library providing the mash data type.
6
6
  See the code for basic documentation.
data/lib/reality/mash.rb CHANGED
@@ -23,7 +23,7 @@ module Reality
23
23
  end
24
24
 
25
25
  def to_h
26
- basic_types = [Fixnum, Float, TrueClass, FalseClass, NilClass]
26
+ basic_types = [Integer, Float, TrueClass, FalseClass, NilClass]
27
27
  result = {}
28
28
  each_pair do |key, value|
29
29
  result[key] = value.is_a?(Mash) ? value.to_h : basic_types.include?(value.class) ? value : value.dup
data/reality-mash.gemspec CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  Gem::Specification.new do |s|
4
4
  s.name = %q{reality-mash}
5
- s.version = '1.0.0'
5
+ s.version = '1.1.0'
6
6
  s.platform = Gem::Platform::RUBY
7
7
 
8
8
  s.authors = ['Peter Donald']
@@ -15,10 +15,8 @@ Gem::Specification.new do |s|
15
15
  s.files = `git ls-files`.split("\n")
16
16
  s.test_files = `git ls-files -- {spec}/*`.split("\n")
17
17
  s.executables = `git ls-files -- bin/*`.split("\n").map { |f| File.basename(f) }
18
- s.default_executable = []
19
18
  s.require_paths = %w(lib)
20
19
 
21
- s.has_rdoc = false
22
20
  s.rdoc_options = %w(--line-numbers --inline-source --title reality-mash)
23
21
 
24
22
  s.add_development_dependency(%q<minitest>, ['= 5.9.1'])
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: reality-mash
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.0.0
4
+ version: 1.1.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Peter Donald
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2016-11-30 00:00:00.000000000 Z
11
+ date: 2021-02-12 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: minitest
@@ -45,9 +45,11 @@ extensions: []
45
45
  extra_rdoc_files: []
46
46
  files:
47
47
  - ".gitattributes"
48
+ - ".github/ISSUE_TEMPLATE.md"
48
49
  - ".gitignore"
49
50
  - ".ruby-version"
50
51
  - ".travis.yml"
52
+ - CODE_OF_CONDUCT.md
51
53
  - CONTRIBUTING.md
52
54
  - Gemfile
53
55
  - LICENSE
@@ -79,8 +81,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
79
81
  - !ruby/object:Gem::Version
80
82
  version: '0'
81
83
  requirements: []
82
- rubyforge_project:
83
- rubygems_version: 2.5.1
84
+ rubygems_version: 3.0.3
84
85
  signing_key:
85
86
  specification_version: 4
86
87
  summary: A library providing the mash data type.