reality-generators 1.14.0 → 1.15.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 3b72487b0475fa8850a257ce3e5775dcace591df
-  data.tar.gz: ee8e609a2ab2ecbdeccab1a064eb2d1f2afc6105
+  metadata.gz: db110ace31f8a0679597105e5c39b515e81dfa5b
+  data.tar.gz: 70cd828d3282e53ee84a111d888317b9f3426a1f
 SHA512:
-  metadata.gz: aeee4f1cbc4a8c8ca738312a64e81cec33d961ef359b8c40d0fa5aa1442cae5a2909f569ac232827a50a5511b30349da7a36e6359765ba012a709a9ab5eda729
-  data.tar.gz: 3fcbe160f190a9cf4ec40bafd094ecf73b8bc3d76da0b346407fd6f34b6ad164a2950a685417cf25b9f3196d1786cb49d5b56ea409445263eaff730d3a0da5d4
+  metadata.gz: 32363bef14842d8f60428757684cc25d4fa8242d2d2407f47426e250a8c99498111bdc3506e94770f62ff886f7a372abff5c64de5358152dda74f7bac1590534
+  data.tar.gz: 1f0319322958462d6203e2cb5673b91e58f5c1d7f890b4db3a27095204f2c71d5b9a6568d3fa420de25ce2e7ebe1e3ead299ed15396eb5878885e3359b6e70bf

data/.gitattributes

@@ -1,6 +1,13 @@
+# DO NOT EDIT: File is auto-generated
 * -text
-*.rb text -crlf -binary
-*.rdoc text -crlf -binary
-*.textile text -crlf -binary
-*.txt text -crlf -binary
-*.erb text -crlf -binary
+*.erb text
+*.gemspec text
+*.md text
+*.rb text
+*.yml text
+.gitattributes text
+.gitignore text
+.ruby-version text
+Gemfile text
+LICENSE text
+Rakefile text

data/.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,47 @@
+<!--
+Thanks for your interest in the project. I appreciate bugs filed and PRs submitted!
+Please make sure that you are familiar with and follow the Code of Conduct for
+this project (found in the CODE_OF_CONDUCT.md file).
+
+Please fill out this template with all the relevant information so we can
+understand what's going on and fix the issue.
+
+I may ask you to submit the fix (after giving some direction).
+-->
+
+Environment:
+
+<!--
+  Please provide the version of this project where the issue occurred as well as the
+  versions of other environmental factors. This could be virtual machine version, os
+  version, browser version etc.
+-->
+
+Relevant code or config:
+
+```
+
+```
+
+What you did:
+
+
+
+What happened:
+
+<!-- Please provide the full error message/screenshots/anything -->
+
+Reproduction repository:
+
+<!--
+If possible, please create a repository that reproduces the issue with the
+minimal amount of code possible. It is highly recommended you take the time
+to read "How to create a Minimal, Complete, and Verifiable example" at
+https://stackoverflow.com/help/mcve
+-->
+
+Problem description:
+
+
+
+Suggested solution:

data/.travis.yml

@@ -1,10 +1,9 @@
 language: ruby
-sudo: false
 rvm:
   - 2.3.1
   - jruby-19mode
 jdk:
-  - oraclejdk7
+  - oraclejdk8
 git:
   depth: 10
 before_install:

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,73 @@
+# 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,
+education, socio-economic status, 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 peter@realityforge.org. 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 https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org

data/CONTRIBUTING.md

@@ -1,19 +1,34 @@
 # How to Contribute
 
-Pull requests are greatly appreciated and are what makes opensource great. Here's a quick guide:
+We'd love to accept your patches and contributions to this project. Pull requests are part of
+what makes open source great. There are just a few small guidelines you need to follow.
 
-* Fork it
-* Create your feature branch (`git checkout -b my-new-feature`)
-* Commit your changes (`git commit -am 'Add some feature'`)
-* Push to the branch (`git push origin my-new-feature`)
-* Create new Pull Request
+## Code of Conduct
 
-Pester us if we don't get your Pull Requests merged in a timely fashion. :)
+Participation in this project comes under the [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md)
+
+## Submitting code via Pull Requests
+
+- We follow the [Github Pull Request Model](https://help.github.com/articles/about-pull-requests/) for
+  all contributions.
+- For large bodies of work, we recommend creating an issue outlining the feature that you wish to build,
+  and describing how it will be implemented. This gives a chance for review to happen early, and ensures
+  no wasted effort occurs.
+- All submissions, will require review before being merged.
+- Finally - *Thanks* for considering submitting code to the project!
+
+## Formatting
+
+When submitting pull requests, make sure to do the following:
+
+- Maintain the same code style as the rest of the project.
+- Remove trailing whitespace. Many editors will do this automatically.
+- Ensure any new files have [a trailing newline](https://stackoverflow.com/questions/5813311/no-newline-at-end-of-file)
 
 ## How to speed the merging of pull requests
 
-* Describe your changes in the CHANGELOG.
-* Give yourself some credit in the appropriate place (usually the CHANGELOG).
+* Describe your changes in the CHANGELOG.md (if present).
+* Give yourself some credit in the appropriate place (usually the CHANGELOG.md).
 * Make commits of logical units.
 * Ensure your commit messages help others understand what you are doing and why.
 * 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. :)
 ## Additional Resources
 
 * [General GitHub documentation](http://help.github.com/)
-* [GitHub pull request documentation](http://help.github.com/send-pull-requests/)
+* [How to write a good Git Commit message](https://chris.beams.io/posts/git-commit/) -
+  Great way to make sure your Pull Requests get accepted.
+* [An Open Source Etiquette Guidebook](https://css-tricks.com/open-source-etiquette-guidebook/#article-header-id-1)

data/README.md

@@ -1,6 +1,6 @@
 # reality-generators
 
-[![Build Status](https://secure.travis-ci.org/realityforge/reality-generators.png?branch=master)](http://travis-ci.org/realityforge/reality-generators)
+[![Build Status](https://secure.travis-ci.org/realityforge/reality-generators.svg?branch=master)](http://travis-ci.org/realityforge/reality-generators)
 
 A basic toolkit for abstracting the generation of files from model objects. These classes
 were extracted from several existing toolkits, primarily [Domgen](https://github.com/realityforge/domgen).
@@ -22,7 +22,7 @@ the generation. These templates types included in the base framework include;
 
 * `ErbTemplate` - Output is generated using an `ERB` template. The model object is supplied as an instance
   method in the templates context.
-* `RubyTemplate` - Output is generated by loading a ruby file to define a module and calling a method 
+* `RubyTemplate` - Output is generated by loading a ruby file to define a module and calling a method
   supplying the model object as a parameter. The method returns the file contents as a string.
 
 Templates are typically defined as rules such as; all models of a particular type, matching a particular
@@ -35,13 +35,13 @@ but these vary based on the particular template type but commonly include:
   on a particular model object instance.
 * `facets` - A list of `facets` that must be enabled on the model object instance for the template
   to be applied. This is in effect a standardized `guard`. Almost all templates will define a list
-  of required `facets` but very few will supply a custom `guard` so that the `facets` attribute 
+  of required `facets` but very few will supply a custom `guard` so that the `facets` attribute
   is just shorthand for a common pattern.
 * `output_filename_pattern` - A ruby string that is evaluated to determine the output filename for
   a particular model object instance. This is only applicable for templates that generate a single file.
 * `target` - A short name that selects the type of model objects against which template should
   run. See below for more details.
-* `template_filename` - The filename of the file that template loads if it loads one. 
+* `template_filename` - The filename of the file that template loads if it loads one.
 
 ## Targets
 

data/lib/reality/generators.rb

@@ -16,7 +16,6 @@ require 'erb'
 
 require 'reality/core'
 require 'reality/naming'
-require 'reality/orderedhash'
 
 require 'reality/generators/core'
 require 'reality/generators/render_context'

data/lib/reality/generators/template_set.rb

@@ -57,7 +57,7 @@ module Reality #nodoc
       end
 
       def template_map
-        @templates ||= Reality::OrderedHash.new
+        @templates ||= {}
       end
     end
   end

data/lib/reality/generators/template_set_container.rb

@@ -79,7 +79,7 @@ module Reality #nodoc
       private
 
       def template_set_map
-        @template_sets ||= Reality::OrderedHash.new
+        @template_sets ||= {}
       end
     end
   end

data/reality-generators.gemspec

@@ -2,7 +2,7 @@
 
 Gem::Specification.new do |s|
   s.name               = %q{reality-generators}
-  s.version            = '1.14.0'
+  s.version            = '1.15.0'
   s.platform           = Gem::Platform::RUBY
 
   s.authors            = ['Peter Donald']
@@ -15,15 +15,12 @@ Gem::Specification.new do |s|
   s.files              = `git ls-files`.split("\n")
   s.test_files         = `git ls-files -- {spec}/*`.split("\n")
   s.executables        = `git ls-files -- bin/*`.split("\n").map { |f| File.basename(f) }
-  s.default_executable = []
   s.require_paths      = %w(lib)
 
-  s.has_rdoc           = false
   s.rdoc_options       = %w(--line-numbers --inline-source --title reality-generators)
 
   s.add_dependency 'reality-core', '>= 1.7.0'
   s.add_dependency 'reality-naming', '>= 1.9.0'
-  s.add_dependency 'reality-orderedhash', '>= 1.0.0'
 
   s.add_development_dependency(%q<minitest>, ['= 5.9.1'])
   s.add_development_dependency(%q<test-unit>, ['= 3.1.5'])

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: reality-generators
 version: !ruby/object:Gem::Version
-  version: 1.14.0
+  version: 1.15.0
 platform: ruby
 authors:
 - Peter Donald
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2017-06-21 00:00:00.000000000 Z
+date: 2019-05-06 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: reality-core
@@ -38,20 +38,6 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: 1.9.0
-- !ruby/object:Gem::Dependency
-  name: reality-orderedhash
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: 1.0.0
-  type: :runtime
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: 1.0.0
 - !ruby/object:Gem::Dependency
   name: minitest
   requirement: !ruby/object:Gem::Requirement
@@ -87,9 +73,11 @@ extensions: []
 extra_rdoc_files: []
 files:
 - ".gitattributes"
+- ".github/ISSUE_TEMPLATE.md"
 - ".gitignore"
 - ".ruby-version"
 - ".travis.yml"
+- CODE_OF_CONDUCT.md
 - CONTRIBUTING.md
 - Gemfile
 - LICENSE