legion-json 1.1.7 → 1.2.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
  SHA256:
3
- metadata.gz: a0fe907b6559d3ede99ddb7da31e1fc3a82aee2bb82193e59d14670b1d1196e0
4
- data.tar.gz: 0f9464fbd3c9acda7449f7e1443090e081762322fea248ee82f16840cc994674
3
+ metadata.gz: a311ed10affbc674c08cc97946b5085124a18eef12063a2251fc56ba1e0ab1ea
4
+ data.tar.gz: 19dec28ecc80573ef9869b78d2a8a51a886e32c1e71c12b82c69e547d59f5593
5
5
  SHA512:
6
- metadata.gz: f1106bc540da7e8cf20ad5063d05a5ed820f3c0c23149e3a1080422bfc3b0476fbbe168f8a2f57a3627cb27eae3801b0ebb99077e8aeb3d73d3e0814ab64864c
7
- data.tar.gz: 3d4acd0e81fe28055e113f8bcaeee0122c0b8c3e200d0735488642fcbc65f9dce96d1509eb9c7f6014a629e5a2a73e4c9b98b61df4490dd2db431c229da45e2b
6
+ metadata.gz: 9659cdb65d8c4e0a0ae1538f4719a8a646e4674debacf7b99cbb64afac3223dc69e731e05cdd32d54e3ee33f134bd4c294108080ea46c84d819d13794acfa3a2
7
+ data.tar.gz: 24bcb5e6dfe3bc7ed25f6aeaa35577d3ec57fc95eefe024dde6ce72986d6c00ec58181c191727de73321e85fcd7e3dafc04d7f57223ab3a16f8aab9d546721d4
@@ -0,0 +1,20 @@
1
+ name: Sourcehawk Scan
2
+ on:
3
+ push:
4
+ branches:
5
+ - main
6
+ - master
7
+ pull_request:
8
+ branches:
9
+ - main
10
+ - master
11
+ jobs:
12
+ build:
13
+ runs-on: ubuntu-latest
14
+ steps:
15
+ - uses: actions/checkout@v2
16
+ - name: Sourcehawk Scan
17
+ uses: optum/sourcehawk-scan-github-action@main
18
+
19
+
20
+
data/.gitignore CHANGED
@@ -1,18 +1,15 @@
1
1
  /.bundle/
2
2
  /.yardoc
3
+ /Gemfile.lock
3
4
  /_yardoc/
4
5
  /coverage/
5
6
  /doc/
6
7
  /pkg/
7
8
  /spec/reports/
8
9
  /tmp/
9
- /rspec/
10
- /test-results/
11
- /.scannerwork
12
- rubocop-result.json
13
- *.gem
14
- *.pem
15
-
10
+ /legion/.idea/
11
+ /.idea/
12
+ *.key
16
13
  # rspec failure tracking
17
14
  .rspec_status
18
-
15
+ legionio.key
data/.rubocop.yml CHANGED
@@ -1,5 +1,7 @@
1
1
  Layout/LineLength:
2
2
  Max: 120
3
+ Exclude:
4
+ - '*.gemspec'
3
5
  Metrics/MethodLength:
4
6
  Max: 30
5
7
  Metrics/ClassLength:
@@ -16,3 +18,5 @@ AllCops:
16
18
  SuggestExtensions: false
17
19
  Style/FrozenStringLiteralComment:
18
20
  Enabled: false
21
+ Gemspec/RequiredRubyVersion:
22
+ Enabled: false
data/CHANGELOG.md ADDED
@@ -0,0 +1,4 @@
1
+ # Legion::JSON
2
+
3
+ ## v1.2.0
4
+ Moving from BitBucket to GitHub inside the Optum org. All git history is reset from this point on
@@ -0,0 +1,75 @@
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
+ nationality, personal appearance, race, religion, or sexual identity and
10
+ 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 email
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 [opensource@optum.com][email]. 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 [http://contributor-covenant.org/version/1/4][version]
72
+
73
+ [homepage]: http://contributor-covenant.org
74
+ [version]: http://contributor-covenant.org/version/1/4/
75
+ [email]: mailto:opensource@optum.com
data/CONTRIBUTING.md ADDED
@@ -0,0 +1,55 @@
1
+ # Contribution Guidelines
2
+
3
+ Please note that this project is released with a [Contributor Code of Conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms. Please also review our [Contributor License Agreement ("CLA")](INDIVIDUAL_CONTRIBUTOR_LICENSE.md) prior to submitting changes to the project. You will need to attest to this agreement following the instructions in the [Paperwork for Pull Requests](#paperwork-for-pull-requests) section below.
4
+
5
+ ---
6
+
7
+ # How to Contribute
8
+
9
+ Now that we have the disclaimer out of the way, let's get into how you can be a part of our project. There are many different ways to contribute.
10
+
11
+ ## Issues
12
+
13
+ We track our work using Issues in GitHub. Feel free to open up your own issue to point out areas for improvement or to suggest your own new experiment. If you are comfortable with signing the waiver linked above and contributing code or documentation, grab your own issue and start working.
14
+
15
+ ## Coding Standards
16
+
17
+ We have some general guidelines towards contributing to this project.
18
+ Please run RSpec and Rubocop while developing code for LegionIO
19
+
20
+ ### Languages
21
+
22
+ *Ruby*
23
+
24
+ ## Pull Requests
25
+
26
+ If you've gotten as far as reading this section, then thank you for your suggestions.
27
+
28
+ ## Paperwork for Pull Requests
29
+
30
+ * Please read this guide and make sure you agree with our [Contributor License Agreement ("CLA")](INDIVIDUAL_CONTRIBUTOR_LICENSE.md).
31
+ * Make sure git knows your name and email address:
32
+ ```
33
+ $ git config user.name "J. Random User"
34
+ $ git config user.email "j.random.user@example.com"
35
+ ```
36
+ >The name and email address must be valid as we cannot accept anonymous contributions.
37
+ * Write good commit messages.
38
+ > Concise commit messages that describe your changes help us better understand your contributions.
39
+ * The first time you open a pull request in this repository, you will see a comment on your PR with a link that will allow you to sign our Contributor License Agreement (CLA) if necessary.
40
+ > The link will take you to a page that allows you to view our CLA. You will need to click the `Sign in with GitHub to agree button` and authorize the cla-assistant application to access the email addresses associated with your GitHub account. Agreeing to the CLA is also considered to be an attestation that you either wrote or have the rights to contribute the code. All committers to the PR branch will be required to sign the CLA, but you will only need to sign once. This CLA applies to all repositories in the Optum org.
41
+
42
+ ## General Guidelines
43
+
44
+ Ensure your pull request (PR) adheres to the following guidelines:
45
+
46
+ * Try to make the name concise and descriptive.
47
+ * Give a good description of the change being made. Since this is very subjective, see the [Updating Your Pull Request (PR)](#updating-your-pull-request-pr) section below for further details.
48
+ * Every pull request should be associated with one or more issues. If no issue exists yet, please create your own.
49
+ * Make sure that all applicable issues are mentioned somewhere in the PR description. This can be done by typing # to bring up a list of issues.
50
+
51
+ ### Updating Your Pull Request (PR)
52
+
53
+ A lot of times, making a PR adhere to the standards above can be difficult. If the maintainers notice anything that we'd like changed, we'll ask you to edit your PR before we merge it. This applies to both the content documented in the PR and the changed contained within the branch being merged. There's no need to open a new PR. Just edit the existing one.
54
+
55
+ [email]: mailto:opensource@optum.com
data/Gemfile CHANGED
@@ -1,7 +1,6 @@
1
1
  source 'https://rubygems.org'
2
2
 
3
3
  gemspec
4
-
5
4
  group :test do
6
5
  gem 'rake'
7
6
  gem 'rspec'
@@ -0,0 +1,30 @@
1
+ # Individual Contributor License Agreement ("Agreement") V2.0
2
+
3
+ Thank you for your interest in this Optum project (the "PROJECT"). In order to clarify the intellectual property license granted with Contributions from any person or entity, the PROJECT must have a Contributor License Agreement ("CLA") on file that has been signed by each Contributor, indicating agreement to the license terms below. This license is for your protection as a Contributor as well as the protection of the PROJECT and its users; it does not change your rights to use your own Contributions for any other purpose.
4
+
5
+ You accept and agree to the following terms and conditions for Your present and future Contributions submitted to the PROJECT. In return, the PROJECT shall not use Your Contributions in a way that is inconsistent with stated project goals in effect at the time of the Contribution. Except for the license granted herein to the PROJECT and recipients of software distributed by the PROJECT, You reserve all right, title, and interest in and to Your Contributions.
6
+ 1. Definitions.
7
+
8
+ "You" (or "Your") shall mean the copyright owner or legal entity authorized by the copyright owner that is making this Agreement with the PROJECT. For legal entities, the entity making a Contribution and all other entities that control, are controlled by, or are under common control with that entity are considered to be a single Contributor. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
9
+
10
+ "Contribution" shall mean any original work of authorship, including any modifications or additions to an existing work, that is intentionally submitted by You to the PROJECT for inclusion in, or documentation of, any of the products owned or managed by the PROJECT (the "Work"). For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the PROJECT or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the PROJECT for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by You as "Not a Contribution."
11
+
12
+ 2. Grant of Copyright License.
13
+
14
+ Subject to the terms and conditions of this Agreement, You hereby grant to the PROJECT and to recipients of software distributed by the PROJECT a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Your Contributions and such derivative works.
15
+
16
+ 3. Grant of Patent License.
17
+
18
+ Subject to the terms and conditions of this Agreement, You hereby grant to the PROJECT and to recipients of software distributed by the PROJECT a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by You that are necessarily infringed by Your Contribution(s) alone or by combination of Your Contribution(s) with the Work to which such Contribution(s) was submitted. If any entity institutes patent litigation against You or any other entity (including a cross-claim or counterclaim in a lawsuit) alleging that your Contribution, or the Work to which you have contributed, constitutes direct or contributory patent infringement, then any patent licenses granted to that entity under this Agreement for that Contribution or Work shall terminate as of the date such litigation is filed.
19
+
20
+ 4. Representations.
21
+
22
+ (a) You represent that you are legally entitled to grant the above license. If your employer(s) has rights to intellectual property that you create that includes your Contributions, you represent that you have received permission to make Contributions on behalf of that employer, that your employer has waived such rights for your Contributions to the PROJECT, or that your employer has executed a separate Corporate CLA with the PROJECT.
23
+
24
+ (b) You represent that each of Your Contributions is Your original creation (see section 6 for submissions on behalf of others). You represent that Your Contribution submissions include complete details of any third-party license or other restriction (including, but not limited to, related patents and trademarks) of which you are personally aware and which are associated with any part of Your Contributions.
25
+
26
+ 5. You are not expected to provide support for Your Contributions, except to the extent You desire to provide support. You may provide support for free, for a fee, or not at all. Unless required by applicable law or agreed to in writing, You provide Your Contributions on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE.
27
+
28
+ 6. Should You wish to submit work that is not Your original creation, You may submit it to the PROJECT separately from any Contribution, identifying the complete details of its source and of any license or other restriction (including, but not limited to, related patents, trademarks, and license agreements) of which you are personally aware, and conspicuously marking the work as "Submitted on behalf of a third-party: [named here]".
29
+
30
+ 7. You agree to notify the PROJECT of any facts or circumstances of which you become aware that would make these representations inaccurate in any respect.
data/LICENSE ADDED
@@ -0,0 +1,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright 2021 Optum
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.
data/NOTICE.txt ADDED
@@ -0,0 +1,9 @@
1
+ Legion::Json(legion-json)
2
+ Copyright 2021 Optum
3
+
4
+ Project Description:
5
+ ====================
6
+ A JSON wrapper module for the LegionIO framework
7
+
8
+ Author(s):
9
+ Esity
data/README.md CHANGED
@@ -1,13 +1,43 @@
1
- # Legion::Json
1
+ Legion::Json
2
+ =====
2
3
 
3
- Legion::Json is part of the Legion Framework
4
- [Issue Tracker - Jira](https://legionio.atlassian.net/projects/JSON/issues)
5
- [Docs - Confluence](https://legionio.atlassian.net/wiki/spaces/LEGION/pages/24674324)
6
- [RubyGems](https://rubygems.org/gems/legion-json)
4
+ Legion::Json is the JSON wrapper that is used by the LegionIO framework. It gives all other gems and extensions a single
5
+ json library to use for consistency. It wraps [multi_json](https://rubygems.org/gems/multi_json) and also [json_pure](https://rubygems.org/gems/json_pure)
7
6
 
8
- ## Usage
9
- This library provides the Legion JSON parser abstraction, enabling the use of platform specific JSON parsers.
10
- Based on the old sensu-json gem
7
+ Additional C extension style json gems can be installed like [oj](https://rubygems.org/gems/oj) and it they should be
8
+ used automatically.
11
9
 
12
- ## License
13
- The gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).
10
+ Supported Ruby versions and implementations
11
+ ------------------------------------------------
12
+
13
+ Legion::Json should work identically on:
14
+
15
+ * JRuby 9.2+
16
+ * Ruby 2.4+
17
+
18
+
19
+ Installation and Usage
20
+ ------------------------
21
+
22
+ You can verify your installation using this piece of code:
23
+
24
+ ```bash
25
+ gem install legion-json
26
+ ```
27
+
28
+ ```ruby
29
+ require 'legion-json'
30
+ json_string = '{"foo":"bar","nested":{"hello":"world"}}'
31
+ Legion::Json.load(json_string)
32
+ Legion::Json.load(json_string, symbolize_keys: false) # symbolize_keys defaults to true
33
+
34
+ hash = {foo: 'bar', nested: {hello: 'world'}}
35
+ Legion::Json.dump(hash)
36
+ Legion::Json.dump(hash, )
37
+
38
+ ```
39
+
40
+ Authors
41
+ ----------
42
+
43
+ * [Matthew Iverson](https://github.com/Esity) - current maintainer
data/SECURITY.md ADDED
@@ -0,0 +1,9 @@
1
+ # Security Policy
2
+
3
+ ## Supported Versions
4
+ | Version | Supported |
5
+ | ------- | ------------------ |
6
+ | 1.x.x | :white_check_mark: |
7
+
8
+ ## Reporting a Vulnerability
9
+ To be added
data/attribution.txt ADDED
@@ -0,0 +1 @@
1
+ Add attributions here.
data/legion-json.gemspec CHANGED
@@ -1,32 +1,31 @@
1
- lib = File.expand_path('lib', __dir__)
2
- $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
3
- require 'legion/json/version'
1
+ # frozen_string_literal: true
2
+
3
+ require_relative 'lib/legion/json/version'
4
4
 
5
5
  Gem::Specification.new do |spec|
6
6
  spec.name = 'legion-json'
7
7
  spec.version = Legion::Json::VERSION
8
8
  spec.authors = ['Esity']
9
- spec.email = ['matthewdiverson@gmail.com']
9
+ spec.email = %w[matthewdiverson@gmail.com ruby@optum.com]
10
10
 
11
- spec.summary = 'Legion JSON'
12
- spec.description = 'A gem used to load and use JSON objects inside the Legion framework'
13
- spec.homepage = 'https://bitbucket.org/legion-io/legion-json'
14
- spec.license = 'MIT'
15
- spec.required_ruby_version = '>= 2.5'
11
+ spec.summary = 'Wraps multi_json, json_pure and others to allow for interchanging json gems without deploying all new extensions'
12
+ spec.description = 'A JSON wrapper module for the LegionIO framework'
13
+ spec.homepage = 'https://github.com/Optum/legion-json'
14
+ spec.license = 'Apache-2.0'
15
+ spec.require_paths = ['lib']
16
+ spec.required_ruby_version = '>= 2.4'
17
+ spec.files = `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
18
+ spec.test_files = spec.files.select { |p| p =~ %r{^test/.*_test.rb} }
19
+ spec.extra_rdoc_files = %w[README.md LICENSE CHANGELOG.md]
16
20
  spec.metadata = {
17
- 'bug_tracker_uri' => 'https://legionio.atlassian.net/projects/JSON/issues',
18
- 'changelog_uri' => 'https://legionio.atlassian.net/wiki/spaces/LEGION/pages/24674324/JSON',
19
- 'documentation_uri' => 'https://legionio.atlassian.net/wiki/spaces/LEGION/pages/24674324/JSON',
20
- 'homepage_uri' => 'https://legionio.atlassian.net/wiki/spaces/LEGION',
21
- 'source_code_uri' => 'https://bitbucket.org/legion-io/legion-json',
22
- 'wiki_uri' => 'https://legionio.atlassian.net/wiki/spaces/LEGION/pages/24674324/JSON'
21
+ 'bug_tracker_uri' => 'https://github.com/Optum/legion-json/issues',
22
+ 'changelog_uri' => 'https://github.com/Optum/legion-json/src/main/CHANGELOG.md',
23
+ 'documentation_uri' => 'https://github.com/Optum/legion-json',
24
+ 'homepage_uri' => 'https://github.com/Optum/LegionIO',
25
+ 'source_code_uri' => 'https://github.com/Optum/legion-json',
26
+ 'wiki_uri' => 'https://github.com/Optum/legion-json/wiki'
23
27
  }
24
28
 
25
- spec.files = `git ls-files -z`.split("\x0").reject do |f|
26
- f.match(%r{^(test|spec|features)/})
27
- end
28
- spec.require_paths = ['lib']
29
-
30
29
  spec.add_dependency 'json_pure'
31
30
  spec.add_dependency 'multi_json'
32
31
  end
data/lib/legion/json.rb CHANGED
@@ -1,23 +1,26 @@
1
1
  require 'legion/json/version'
2
2
  require 'legion/json/parse_error'
3
+ require 'legion/json/invalid_json'
4
+ require 'json'
3
5
  require 'multi_json'
4
6
 
5
7
  module Legion
6
8
  module JSON
7
- class << self
8
- def parser
9
- @parser ||= MultiJson
10
- end
9
+ def parser
10
+ @parser ||= MultiJson
11
+ end
12
+ module_function :parser
11
13
 
12
- def load(string, symbolize_keys = true)
13
- MultiJson.load(string, symbolize_keys: symbolize_keys)
14
- rescue StandardError => e
15
- raise Legion::JSON::ParseError.build(e, string)
16
- end
14
+ def load(string, symbolize_keys: true)
15
+ parser.load(string, symbolize_keys: symbolize_keys)
16
+ rescue StandardError => e
17
+ raise Legion::JSON::ParseError.build(e, string)
18
+ end
19
+ module_function :load
17
20
 
18
- def dump(object, pretty = false)
19
- parser.dump(object, pretty: pretty)
20
- end
21
+ def dump(object, pretty: false)
22
+ parser.dump(object, pretty: pretty)
21
23
  end
24
+ module_function :dump
22
25
  end
23
26
  end
@@ -0,0 +1,5 @@
1
+ module Legion
2
+ module Exception
3
+ class InvalidJson < StandardError; end
4
+ end
5
+ end
@@ -1,5 +1,5 @@
1
1
  module Legion
2
2
  module Json
3
- VERSION = '1.1.7'.freeze
3
+ VERSION = '1.2.0'.freeze
4
4
  end
5
5
  end
data/sourcehawk.yml ADDED
@@ -0,0 +1,4 @@
1
+
2
+ config-locations:
3
+ - https://raw.githubusercontent.com/optum/.github/main/sourcehawk.yml
4
+
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: legion-json
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.1.7
4
+ version: 1.2.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Esity
8
- autorequire:
8
+ autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2021-05-28 00:00:00.000000000 Z
11
+ date: 2021-06-04 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: json_pure
@@ -38,35 +38,48 @@ dependencies:
38
38
  - - ">="
39
39
  - !ruby/object:Gem::Version
40
40
  version: '0'
41
- description: A gem used to load and use JSON objects inside the Legion framework
41
+ description: A JSON wrapper module for the LegionIO framework
42
42
  email:
43
43
  - matthewdiverson@gmail.com
44
+ - ruby@optum.com
44
45
  executables: []
45
46
  extensions: []
46
- extra_rdoc_files: []
47
+ extra_rdoc_files:
48
+ - README.md
49
+ - LICENSE
50
+ - CHANGELOG.md
47
51
  files:
52
+ - ".github/workflows/sourcehawk-scan.yml"
48
53
  - ".gitignore"
49
54
  - ".rubocop.yml"
55
+ - CHANGELOG.md
56
+ - CODE_OF_CONDUCT.md
57
+ - CONTRIBUTING.md
50
58
  - Gemfile
51
- - LICENSE.txt
59
+ - INDIVIDUAL_CONTRIBUTOR_LICENSE.md
60
+ - LICENSE
61
+ - NOTICE.txt
52
62
  - README.md
53
- - bitbucket-pipelines.yml
63
+ - SECURITY.md
64
+ - attribution.txt
54
65
  - legion-json.gemspec
55
66
  - lib/legion/json.rb
67
+ - lib/legion/json/invalid_json.rb
56
68
  - lib/legion/json/parse_error.rb
57
69
  - lib/legion/json/version.rb
58
70
  - sonar-project.properties
59
- homepage: https://bitbucket.org/legion-io/legion-json
71
+ - sourcehawk.yml
72
+ homepage: https://github.com/Optum/legion-json
60
73
  licenses:
61
- - MIT
74
+ - Apache-2.0
62
75
  metadata:
63
- bug_tracker_uri: https://legionio.atlassian.net/projects/JSON/issues
64
- changelog_uri: https://legionio.atlassian.net/wiki/spaces/LEGION/pages/24674324/JSON
65
- documentation_uri: https://legionio.atlassian.net/wiki/spaces/LEGION/pages/24674324/JSON
66
- homepage_uri: https://legionio.atlassian.net/wiki/spaces/LEGION
67
- source_code_uri: https://bitbucket.org/legion-io/legion-json
68
- wiki_uri: https://legionio.atlassian.net/wiki/spaces/LEGION/pages/24674324/JSON
69
- post_install_message:
76
+ bug_tracker_uri: https://github.com/Optum/legion-json/issues
77
+ changelog_uri: https://github.com/Optum/legion-json/src/main/CHANGELOG.md
78
+ documentation_uri: https://github.com/Optum/legion-json
79
+ homepage_uri: https://github.com/Optum/LegionIO
80
+ source_code_uri: https://github.com/Optum/legion-json
81
+ wiki_uri: https://github.com/Optum/legion-json/wiki
82
+ post_install_message:
70
83
  rdoc_options: []
71
84
  require_paths:
72
85
  - lib
@@ -74,7 +87,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
74
87
  requirements:
75
88
  - - ">="
76
89
  - !ruby/object:Gem::Version
77
- version: '2.5'
90
+ version: '2.4'
78
91
  required_rubygems_version: !ruby/object:Gem::Requirement
79
92
  requirements:
80
93
  - - ">="
@@ -82,7 +95,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
82
95
  version: '0'
83
96
  requirements: []
84
97
  rubygems_version: 3.1.6
85
- signing_key:
98
+ signing_key:
86
99
  specification_version: 4
87
- summary: Legion JSON
100
+ summary: Wraps multi_json, json_pure and others to allow for interchanging json gems
101
+ without deploying all new extensions
88
102
  test_files: []
data/LICENSE.txt DELETED
@@ -1,21 +0,0 @@
1
- The MIT License (MIT)
2
-
3
- Copyright (c) 2018 Miverson
4
-
5
- Permission is hereby granted, free of charge, to any person obtaining a copy
6
- of this software and associated documentation files (the "Software"), to deal
7
- in the Software without restriction, including without limitation the rights
8
- to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
- copies of the Software, and to permit persons to whom the Software is
10
- furnished to do so, subject to the following conditions:
11
-
12
- The above copyright notice and this permission notice shall be included in
13
- all copies or substantial portions of the Software.
14
-
15
- THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
- IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
- FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
- AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
- LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
- OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
21
- THE SOFTWARE.
@@ -1,74 +0,0 @@
1
- image: ruby:2.7
2
-
3
-
4
- definitions:
5
- steps:
6
- - step: &rubocop
7
- name: Rubocop
8
- runs-on: self.hosted
9
- script:
10
- - gem install rubocop rubocop-rspec rubocop-performance rubocop-sequel rubocop-md rubocop-sequel --no-document
11
- - rubocop --format junit --out test-reports/junit.xml
12
- - step: &rspec
13
- name: RSpec 2.7
14
- runs-on: self.hosted
15
- caches:
16
- - bundler
17
- script:
18
- - gem install bundler rspec rspec_junit_formatter
19
- - bundle install
20
- - bundle exec rspec --format RspecJunitFormatter --out test-reports/junit.xml
21
- caches:
22
- bundler: /usr/local/bundle
23
-
24
- pipelines:
25
- default:
26
- - step: *rubocop
27
- - step: *rspec
28
- - parallel:
29
- - step:
30
- <<: *rspec
31
- name: RSpec 2.5
32
- image: ruby:2.5
33
- - step:
34
- <<: *rspec
35
- name: RSpec 2.6
36
- image: ruby:2.6
37
- - step:
38
- <<: *rspec
39
- name: RSpec 3
40
- image: ruby:3
41
- pull-requests:
42
- master:
43
- - step: *rubocop
44
- - step: *rspec
45
- - parallel:
46
- - step:
47
- <<: *rspec
48
- name: RSpec 2.5
49
- image: ruby:2.5
50
- - step:
51
- <<: *rspec
52
- name: RSpec 2.6
53
- image: ruby:2.6
54
- - step:
55
- <<: *rspec
56
- name: RSpec 3
57
- image: ruby:3
58
- - step:
59
- name: RubyGems Deployment
60
- deployment: RubyGems
61
- runs-on: self.hosted
62
- script:
63
- - gem install gem-release
64
- - (umask 077 ; echo $gem_creds | base64 --decode > ~/.gem/credentials)
65
- - gem release --tag --push
66
- - git push --tags
67
- - gem build
68
- condition:
69
- changesets:
70
- includePaths:
71
- - "lib/legion/json/version.rb"
72
- artifacts:
73
- - pkg/**
74
- - '*.gem'