reality-facets 1.11.0 → 1.12.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
2
  SHA1:
3
- metadata.gz: fab66e2fc2cbcf11caf14a81394eb5c7a85cc0a2
4
- data.tar.gz: ee3c44d80e468af0e794afeb352a0100887e2d8c
3
+ metadata.gz: 67377b98231870d6547157fa2539117a24bc5c54
4
+ data.tar.gz: d7d4904981e111cfc79f0aac45c294894310ea35
5
5
  SHA512:
6
- metadata.gz: f5262030dc60d52c5e706fa52a66365a3731d7a081821ea698b0a7a9575593662c8b63271ff558ddff821b39cdf30678d5808d1f5a4a2518c521ff75518372ba
7
- data.tar.gz: 608f29f6e934c4431a32cbf434184cd571baba53777ce783da2aebd74f70215d5183df6a3c803182edf126d038c1529cb835897da9dd76f0e406c073977eea1c
6
+ metadata.gz: 4358ab32a195bbf489ceb432365577ffe6e122a4cc0141e9f3fc7eee5afcef2f8b28c871818ba8150af009d3863cefbd80e8c003d8ddf871d38c29de29d3150a
7
+ data.tar.gz: 014df1dfd58e3139ed29a945ef7721fd107a3c80e2079fcd738d6d1e4b740e1a849c7e22256405b2863882b07bfe960f43320748bbbcdbf438b533cab5857ba1
@@ -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:
@@ -1,10 +1,6 @@
1
1
  language: ruby
2
- sudo: false
3
2
  rvm:
4
3
  - 2.3.1
5
- - jruby-19mode
6
- jdk:
7
- - oraclejdk7
8
4
  git:
9
5
  depth: 10
10
6
  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
@@ -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-facets
2
2
 
3
- [![Build Status](https://secure.travis-ci.org/realityforge/reality-facets.png?branch=master)](http://travis-ci.org/realityforge/reality-facets)
3
+ [![Build Status](https://secure.travis-ci.org/realityforge/reality-facets.svg?branch=master)](http://travis-ci.org/realityforge/reality-facets)
4
4
 
5
5
  A basic toolkit for binding facets or extensions to model objects. These classes
6
6
  were extracted from several existing toolkits, primarily [Domgen](https://github.com/realityforge/domgen).
@@ -16,7 +16,6 @@ require 'erb'
16
16
 
17
17
  require 'reality/core'
18
18
  require 'reality/naming'
19
- require 'reality/orderedhash'
20
19
 
21
20
  require 'reality/facets/core'
22
21
  require 'reality/facets/target_manager'
@@ -168,7 +168,7 @@ module Reality #nodoc
168
168
 
169
169
  # Map a facet key to a map. The map maps types to extension classes
170
170
  def facet_map
171
- @facets ||= Reality::OrderedHash.new
171
+ @facets ||= {}
172
172
  end
173
173
  end
174
174
  end
@@ -142,7 +142,7 @@ module Reality #nodoc
142
142
  end
143
143
 
144
144
  def target_map
145
- @target_map ||= Reality::OrderedHash.new
145
+ @target_map ||= {}
146
146
  end
147
147
  end
148
148
  end
@@ -2,7 +2,7 @@
2
2
 
3
3
  Gem::Specification.new do |s|
4
4
  s.name = %q{reality-facets}
5
- s.version = '1.11.0'
5
+ s.version = '1.12.0'
6
6
  s.platform = Gem::Platform::RUBY
7
7
 
8
8
  s.authors = ['Peter Donald']
@@ -15,15 +15,12 @@ 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-facets)
23
21
 
24
22
  s.add_dependency 'reality-core', '>= 1.8.0'
25
23
  s.add_dependency 'reality-naming', '>= 1.9.0'
26
- s.add_dependency 'reality-orderedhash', '>= 1.0.0'
27
24
 
28
25
  s.add_development_dependency(%q<minitest>, ['= 5.9.1'])
29
26
  s.add_development_dependency(%q<test-unit>, ['= 3.1.5'])
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: reality-facets
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.11.0
4
+ version: 1.12.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: 2017-10-11 00:00:00.000000000 Z
11
+ date: 2019-05-06 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: reality-core
@@ -38,20 +38,6 @@ dependencies:
38
38
  - - ">="
39
39
  - !ruby/object:Gem::Version
40
40
  version: 1.9.0
41
- - !ruby/object:Gem::Dependency
42
- name: reality-orderedhash
43
- requirement: !ruby/object:Gem::Requirement
44
- requirements:
45
- - - ">="
46
- - !ruby/object:Gem::Version
47
- version: 1.0.0
48
- type: :runtime
49
- prerelease: false
50
- version_requirements: !ruby/object:Gem::Requirement
51
- requirements:
52
- - - ">="
53
- - !ruby/object:Gem::Version
54
- version: 1.0.0
55
41
  - !ruby/object:Gem::Dependency
56
42
  name: minitest
57
43
  requirement: !ruby/object:Gem::Requirement
@@ -87,9 +73,11 @@ extensions: []
87
73
  extra_rdoc_files: []
88
74
  files:
89
75
  - ".gitattributes"
76
+ - ".github/ISSUE_TEMPLATE.md"
90
77
  - ".gitignore"
91
78
  - ".ruby-version"
92
79
  - ".travis.yml"
80
+ - CODE_OF_CONDUCT.md
93
81
  - CONTRIBUTING.md
94
82
  - Gemfile
95
83
  - LICENSE