snaky_hash 2.0.3 → 2.0.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- checksums.yaml.gz.sig +0 -0
- data/CHANGELOG.md +99 -3
- data/CITATION.cff +20 -0
- data/CODE_OF_CONDUCT.md +24 -23
- data/CONTRIBUTING.md +198 -65
- data/FUNDING.md +74 -0
- data/LICENSE.md +10 -0
- data/README.md +346 -302
- data/RUBOCOP.md +71 -0
- data/SECURITY.md +11 -15
- data/certs/pboling.pem +27 -0
- data/lib/snaky_hash/serializer.rb +1 -1
- data/lib/snaky_hash/version.rb +2 -7
- data/sig/snaky_hash/version.rbs +6 -0
- data/sig/snaky_hash.rbs +3 -0
- data.tar.gz.sig +0 -0
- metadata +148 -43
- metadata.gz.sig +0 -0
- data/LICENSE.txt +0 -21
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 62cfadb58311a343c089f9ad6db74917c16da5ed2b061ea614eabc1fb9e58000
|
|
4
|
+
data.tar.gz: 0c25223a8a761b26257be06c454fd1cb129b24920ba155dfa0883404f6b6df7a
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 4c4b2e01be080e9dbda82c6d5fa0fcd7837fab59bc07a042f8ca6b4925c67e589a6ebf68dc747bfaa8292bcb42b826350580c5a9f953c3222ed8652991eaa52a
|
|
7
|
+
data.tar.gz: 144d11ba0a8eac2abb9f4cd465a42ff21cdecd09f69865bcf111d0ec6642d236ad9206aaa030cb4a045e5373023f1af37647aece8ca5bb1a7b9598c7e24696ac
|
checksums.yaml.gz.sig
CHANGED
|
Binary file
|
data/CHANGELOG.md
CHANGED
|
@@ -1,29 +1,98 @@
|
|
|
1
1
|
# Changelog
|
|
2
|
+
|
|
3
|
+
[![SemVer 2.0.0][📌semver-img]][📌semver] [![Keep-A-Changelog 1.0.0][📗keep-changelog-img]][📗keep-changelog]
|
|
4
|
+
|
|
2
5
|
All notable changes to this project will be documented in this file.
|
|
3
6
|
|
|
4
|
-
The format
|
|
5
|
-
and this project adheres to [Semantic Versioning
|
|
7
|
+
The format is based on [Keep a Changelog][📗keep-changelog],
|
|
8
|
+
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html),
|
|
9
|
+
and [yes][📌major-versions-not-sacred], platform and engine support are part of the [public API][📌semver-breaking].
|
|
10
|
+
Please file a bug if you notice a violation of semantic versioning.
|
|
11
|
+
|
|
12
|
+
[📌semver]: https://semver.org/spec/v2.0.0.html
|
|
13
|
+
[📌semver-img]: https://img.shields.io/badge/semver-2.0.0-FFDD67.svg?style=flat
|
|
14
|
+
[📌semver-breaking]: https://github.com/semver/semver/issues/716#issuecomment-869336139
|
|
15
|
+
[📌major-versions-not-sacred]: https://tom.preston-werner.com/2022/05/23/major-version-numbers-are-not-sacred.html
|
|
16
|
+
[📗keep-changelog]: https://keepachangelog.com/en/1.0.0/
|
|
17
|
+
[📗keep-changelog-img]: https://img.shields.io/badge/keep--a--changelog-1.0.0-FFDD67.svg?style=flat
|
|
6
18
|
|
|
7
19
|
## [Unreleased]
|
|
20
|
+
|
|
8
21
|
### Added
|
|
22
|
+
|
|
9
23
|
### Changed
|
|
24
|
+
|
|
10
25
|
### Deprecated
|
|
26
|
+
|
|
11
27
|
### Removed
|
|
28
|
+
|
|
12
29
|
### Fixed
|
|
30
|
+
|
|
13
31
|
### Security
|
|
14
32
|
|
|
33
|
+
## [2.0.6] - 2026-06-11
|
|
34
|
+
|
|
35
|
+
- TAG: [v2.0.6][2.0.6t]
|
|
36
|
+
- COVERAGE: 100.00% -- 133/133 lines in 7 files
|
|
37
|
+
- BRANCH COVERAGE: 100.00% -- 38/38 branches in 7 files
|
|
38
|
+
- 92.86% documented
|
|
39
|
+
|
|
40
|
+
### Fixed
|
|
41
|
+
|
|
42
|
+
- Restored `docs/CNAME` so the generated documentation site keeps its custom domain.
|
|
43
|
+
- Removed stale legacy CI workflows and duplicate extracted-stdlib gem
|
|
44
|
+
declarations from generated Appraisal gemfiles.
|
|
45
|
+
|
|
46
|
+
## [2.0.5] - 2026-06-07
|
|
47
|
+
|
|
48
|
+
- TAG: [v2.0.5][2.0.5t]
|
|
49
|
+
- COVERAGE: 100.00% -- 133/133 lines in 7 files
|
|
50
|
+
- BRANCH COVERAGE: 100.00% -- 38/38 branches in 7 files
|
|
51
|
+
- 92.86% documented
|
|
52
|
+
|
|
53
|
+
### Changed
|
|
54
|
+
|
|
55
|
+
- Refreshed project scaffolding with the current `kettle-jem` template, including
|
|
56
|
+
updated CI workflows, modular gemfiles, and development tooling floors.
|
|
57
|
+
|
|
58
|
+
## [2.0.4] - 2026-05-16
|
|
59
|
+
|
|
60
|
+
- TAG: [v2.0.4][2.0.4t]
|
|
61
|
+
- COVERAGE: 100.00% -- 133/133 lines in 7 files
|
|
62
|
+
- BRANCH COVERAGE: 100.00% -- 38/38 branches in 7 files
|
|
63
|
+
- 100.00% documented
|
|
64
|
+
|
|
65
|
+
### Added
|
|
66
|
+
|
|
67
|
+
- Incident Response Plan in IRP.md
|
|
68
|
+
- SnakyHash::VERSION (Traditional Constant Location)
|
|
69
|
+
- kettle-dev & kettle-test dev harnesses
|
|
70
|
+
|
|
71
|
+
### Changed
|
|
72
|
+
|
|
73
|
+
- Contributor Conenant updated to version 2.1
|
|
74
|
+
|
|
75
|
+
### Fixed
|
|
76
|
+
|
|
77
|
+
- Specs
|
|
78
|
+
|
|
15
79
|
## [2.0.3] - 2025-05-23
|
|
80
|
+
|
|
16
81
|
- TAG: [v2.0.3][2.0.3t]
|
|
17
82
|
- COVERAGE: 100.00% -- 132/132 lines in 7 files
|
|
18
83
|
- BRANCH COVERAGE: 100.00% -- 38/38 branches in 7 files
|
|
19
84
|
- 100.00% documented
|
|
85
|
+
|
|
20
86
|
### Added
|
|
87
|
+
|
|
21
88
|
- `#dump` instance method injected by `extend SnakyHash::Serializer` (@pboling)
|
|
22
89
|
- `dump_hash_extensions` - new feature, analogous to `load_hash_extensions` (@pboling)
|
|
23
90
|
- `dump_value_extensions` - alternate name for `dump_extensions` (@pboling)
|
|
24
91
|
- `load_value_extensions` - alternate name for `load_extensions` (@pboling)
|
|
25
92
|
- Clarifying documentation (@pboling)
|
|
93
|
+
|
|
26
94
|
### Fixed
|
|
95
|
+
|
|
27
96
|
- [gh4](https://github.com/oauth-xx/snaky_hash/pull/4) - Serializer extensions dump and load empty values properly (@pboling)
|
|
28
97
|
- Fixed `dump_extensions`, `load_extensions`, `load_hash_extensions`
|
|
29
98
|
- Intended usage is primarily JSON, and oauth2 gem
|
|
@@ -31,11 +100,14 @@ and this project adheres to [Semantic Versioning v2](https://semver.org/spec/v2.
|
|
|
31
100
|
- Previous logic was inherited from design decisions made by `serialized_hashie` gem; doesn't apply here
|
|
32
101
|
|
|
33
102
|
## [2.0.2] - 2025-05-21
|
|
103
|
+
|
|
34
104
|
- TAG: [v2.0.2][2.0.2t]
|
|
35
105
|
- COVERAGE: 100.00% -- 119/119 lines in 7 files
|
|
36
106
|
- BRANCH COVERAGE: 100.00% -- 35/35 branches in 7 files
|
|
37
107
|
- 100.00% documented
|
|
108
|
+
|
|
38
109
|
### Added
|
|
110
|
+
|
|
39
111
|
- Gem is signed by 20-year cert (@pboling)
|
|
40
112
|
- Expires 2045-04-29
|
|
41
113
|
- Gemspec metadata updates (@pboling)
|
|
@@ -48,42 +120,66 @@ and this project adheres to [Semantic Versioning v2](https://semver.org/spec/v2.
|
|
|
48
120
|
- 100% documented! (@pboling)
|
|
49
121
|
|
|
50
122
|
## [2.0.1] - 2022-09-23
|
|
123
|
+
|
|
51
124
|
- TAG: [v2.0.1][2.0.1t]
|
|
125
|
+
|
|
52
126
|
### Added
|
|
127
|
+
|
|
53
128
|
- Certificate for signing gem releases (@pboling)
|
|
54
129
|
- Gemspec metadata (@pboling)
|
|
55
130
|
- funding_uri
|
|
56
131
|
- mailing_list_uri
|
|
57
132
|
- Checksums for released gems (@pboling)
|
|
133
|
+
|
|
58
134
|
### Changed
|
|
135
|
+
|
|
59
136
|
- Gem releases are now cryptographically signed (@pboling)
|
|
60
137
|
|
|
61
138
|
## [2.0.0] - 2022-08-29
|
|
139
|
+
|
|
62
140
|
- TAG: [v2.0.0][2.0.0t]
|
|
141
|
+
|
|
63
142
|
### Changed
|
|
143
|
+
|
|
64
144
|
- **BREAKING**: `SnakeHash::Snake` is now a mixin, now with support for symbol or string keys
|
|
65
145
|
```ruby
|
|
66
146
|
class MySnakedHash < Hashie::Mash
|
|
67
147
|
include SnakyHash::Snake.new(key_type: :string) # or :symbol
|
|
68
148
|
end
|
|
69
149
|
```
|
|
150
|
+
|
|
70
151
|
### Added
|
|
152
|
+
|
|
71
153
|
- `SnakyHash::StringKeyed`: a Hashie::Mash class with snake-cased String keys
|
|
72
154
|
- `SnakyHash::SymbolKeyed`: a Hashie::Mash class with snake-cased Symbol keys
|
|
73
155
|
|
|
74
156
|
## [1.0.1] - 2022-08-26
|
|
157
|
+
|
|
75
158
|
- TAG: [v1.0.1][1.0.1t]
|
|
159
|
+
|
|
76
160
|
### Added
|
|
161
|
+
|
|
77
162
|
- Missing LICENSE.txt file to release
|
|
163
|
+
|
|
78
164
|
### Removed
|
|
165
|
+
|
|
79
166
|
- Accidentally added bundler dependency (vestige of transpec process) is now removed
|
|
80
167
|
|
|
81
168
|
## [1.0.0] - 2022-08-26
|
|
169
|
+
|
|
82
170
|
- TAG: [v1.0.0][1.0.0t]
|
|
171
|
+
|
|
83
172
|
### Added
|
|
173
|
+
|
|
84
174
|
- Initial release
|
|
85
175
|
|
|
86
|
-
[Unreleased]: https://
|
|
176
|
+
[Unreleased]: https://github.com/ruby-oauth/snaky_hash/compare/v2.0.6...HEAD
|
|
177
|
+
[2.0.6]: https://github.com/ruby-oauth/snaky_hash/compare/v2.0.5...v2.0.6
|
|
178
|
+
[2.0.6t]: https://github.com/ruby-oauth/snaky_hash/releases/tag/v2.0.6
|
|
179
|
+
[2.0.5]: https://github.com/ruby-oauth/snaky_hash/compare/v2.0.4...v2.0.5
|
|
180
|
+
[2.0.5t]: https://github.com/ruby-oauth/snaky_hash/releases/tag/v2.0.5
|
|
181
|
+
[2.0.4]: https://github.com/ruby-oauth/snaky_hash/compare/v2.0.3...v2.0.4
|
|
182
|
+
[2.0.4t]: https://github.com/ruby-oauth/snaky_hash/releases/tag/v2.0.4
|
|
87
183
|
[2.0.3]: https://gitlab.com/oauth-xx/snaky_hash/-/compare/v2.0.2...v2.0.3
|
|
88
184
|
[2.0.3t]: https://gitlab.com/oauth-xx/snaky_hash/-/releases/tag/v2.0.3
|
|
89
185
|
[2.0.2]: https://gitlab.com/oauth-xx/snaky_hash/-/compare/v2.0.1...v2.0.2
|
data/CITATION.cff
ADDED
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
cff-version: 1.2.0
|
|
2
|
+
title: "snaky_hash"
|
|
3
|
+
message: >-
|
|
4
|
+
If you use this work and you want to cite it,
|
|
5
|
+
then you can use the metadata from this file.
|
|
6
|
+
type: software
|
|
7
|
+
authors:
|
|
8
|
+
- given-names: "Peter H."
|
|
9
|
+
family-names: "Boling"
|
|
10
|
+
email: "floss@galtzo.com"
|
|
11
|
+
affiliation: "galtzo.com"
|
|
12
|
+
orcid: 'https://orcid.org/0009-0008-8519-441X'
|
|
13
|
+
identifiers:
|
|
14
|
+
- type: url
|
|
15
|
+
value: 'https://github.com/ruby-oauth/snaky_hash'
|
|
16
|
+
description: "snaky_hash"
|
|
17
|
+
repository-code: 'https://github.com/ruby-oauth/snaky_hash'
|
|
18
|
+
abstract: >-
|
|
19
|
+
snaky_hash
|
|
20
|
+
license: See license file
|
data/CODE_OF_CONDUCT.md
CHANGED
|
@@ -1,4 +1,3 @@
|
|
|
1
|
-
|
|
2
1
|
# Contributor Covenant Code of Conduct
|
|
3
2
|
|
|
4
3
|
## Our Pledge
|
|
@@ -7,8 +6,8 @@ We as members, contributors, and leaders pledge to make participation in our
|
|
|
7
6
|
community a harassment-free experience for everyone, regardless of age, body
|
|
8
7
|
size, visible or invisible disability, ethnicity, sex characteristics, gender
|
|
9
8
|
identity and expression, level of experience, education, socio-economic status,
|
|
10
|
-
nationality, personal appearance, race, religion, or sexual
|
|
11
|
-
and orientation.
|
|
9
|
+
nationality, personal appearance, race, caste, color, religion, or sexual
|
|
10
|
+
identity and orientation.
|
|
12
11
|
|
|
13
12
|
We pledge to act and interact in ways that contribute to an open, welcoming,
|
|
14
13
|
diverse, inclusive, and healthy community.
|
|
@@ -23,17 +22,17 @@ community include:
|
|
|
23
22
|
* Giving and gracefully accepting constructive feedback
|
|
24
23
|
* Accepting responsibility and apologizing to those affected by our mistakes,
|
|
25
24
|
and learning from the experience
|
|
26
|
-
* Focusing on what is best not just for us as individuals, but for the
|
|
27
|
-
|
|
25
|
+
* Focusing on what is best not just for us as individuals, but for the overall
|
|
26
|
+
community
|
|
28
27
|
|
|
29
28
|
Examples of unacceptable behavior include:
|
|
30
29
|
|
|
31
|
-
* The use of sexualized language or imagery, and sexual attention or
|
|
32
|
-
|
|
30
|
+
* The use of sexualized language or imagery, and sexual attention or advances of
|
|
31
|
+
any kind
|
|
33
32
|
* Trolling, insulting or derogatory comments, and personal or political attacks
|
|
34
33
|
* Public or private harassment
|
|
35
|
-
* Publishing others' private information, such as a physical or email
|
|
36
|
-
|
|
34
|
+
* Publishing others' private information, such as a physical or email address,
|
|
35
|
+
without their explicit permission
|
|
37
36
|
* Other conduct which could reasonably be considered inappropriate in a
|
|
38
37
|
professional setting
|
|
39
38
|
|
|
@@ -53,7 +52,7 @@ decisions when appropriate.
|
|
|
53
52
|
|
|
54
53
|
This Code of Conduct applies within all community spaces, and also applies when
|
|
55
54
|
an individual is officially representing the community in public spaces.
|
|
56
|
-
Examples of representing our community include using an official
|
|
55
|
+
Examples of representing our community include using an official email address,
|
|
57
56
|
posting via an official social media account, or acting as an appointed
|
|
58
57
|
representative at an online or offline event.
|
|
59
58
|
|
|
@@ -61,7 +60,7 @@ representative at an online or offline event.
|
|
|
61
60
|
|
|
62
61
|
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
|
63
62
|
reported to the community leaders responsible for enforcement at
|
|
64
|
-
[
|
|
63
|
+
[![Contact Maintainer][🚂maint-contact-img]][🚂maint-contact].
|
|
65
64
|
All complaints will be reviewed and investigated promptly and fairly.
|
|
66
65
|
|
|
67
66
|
All community leaders are obligated to respect the privacy and security of the
|
|
@@ -83,15 +82,15 @@ behavior was inappropriate. A public apology may be requested.
|
|
|
83
82
|
|
|
84
83
|
### 2. Warning
|
|
85
84
|
|
|
86
|
-
**Community Impact**: A violation through a single incident or series
|
|
87
|
-
|
|
85
|
+
**Community Impact**: A violation through a single incident or series of
|
|
86
|
+
actions.
|
|
88
87
|
|
|
89
88
|
**Consequence**: A warning with consequences for continued behavior. No
|
|
90
89
|
interaction with the people involved, including unsolicited interaction with
|
|
91
90
|
those enforcing the Code of Conduct, for a specified period of time. This
|
|
92
91
|
includes avoiding interactions in community spaces as well as external channels
|
|
93
|
-
like social media. Violating these terms may lead to a temporary or
|
|
94
|
-
|
|
92
|
+
like social media. Violating these terms may lead to a temporary or permanent
|
|
93
|
+
ban.
|
|
95
94
|
|
|
96
95
|
### 3. Temporary Ban
|
|
97
96
|
|
|
@@ -107,27 +106,29 @@ Violating these terms may lead to a permanent ban.
|
|
|
107
106
|
### 4. Permanent Ban
|
|
108
107
|
|
|
109
108
|
**Community Impact**: Demonstrating a pattern of violation of community
|
|
110
|
-
standards, including sustained inappropriate behavior,
|
|
109
|
+
standards, including sustained inappropriate behavior, harassment of an
|
|
111
110
|
individual, or aggression toward or disparagement of classes of individuals.
|
|
112
111
|
|
|
113
|
-
**Consequence**: A permanent ban from any sort of public interaction within
|
|
114
|
-
|
|
112
|
+
**Consequence**: A permanent ban from any sort of public interaction within the
|
|
113
|
+
community.
|
|
115
114
|
|
|
116
115
|
## Attribution
|
|
117
116
|
|
|
118
117
|
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
|
|
119
|
-
version 2.
|
|
120
|
-
[https://www.contributor-covenant.org/version/2/
|
|
118
|
+
version 2.1, available at
|
|
119
|
+
[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
|
|
121
120
|
|
|
122
121
|
Community Impact Guidelines were inspired by
|
|
123
122
|
[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
|
|
124
123
|
|
|
125
124
|
For answers to common questions about this code of conduct, see the FAQ at
|
|
126
|
-
[https://www.contributor-covenant.org/faq][FAQ]. Translations are available
|
|
127
|
-
|
|
125
|
+
[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
|
|
126
|
+
[https://www.contributor-covenant.org/translations][translations].
|
|
128
127
|
|
|
129
128
|
[homepage]: https://www.contributor-covenant.org
|
|
130
|
-
[v2.
|
|
129
|
+
[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
|
|
131
130
|
[Mozilla CoC]: https://github.com/mozilla/diversity
|
|
132
131
|
[FAQ]: https://www.contributor-covenant.org/faq
|
|
133
132
|
[translations]: https://www.contributor-covenant.org/translations
|
|
133
|
+
[🚂maint-contact]: http://www.railsbling.com/contact
|
|
134
|
+
[🚂maint-contact-img]: https://img.shields.io/badge/Contact-Maintainer-0093D0.svg?style=flat&logo=rubyonrails&logoColor=red
|