sane_patch 0.1.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +7 -0
- data/.gitignore +11 -0
- data/.rspec +3 -0
- data/.travis.yml +7 -0
- data/CODE_OF_CONDUCT.md +74 -0
- data/Gemfile +4 -0
- data/Gemfile.lock +35 -0
- data/LICENSE.txt +21 -0
- data/README.md +115 -0
- data/Rakefile +6 -0
- data/lib/sane_patch.rb +22 -0
- data/lib/sane_patch/version.rb +3 -0
- data/sane_patch.gemspec +39 -0
- metadata +100 -0
checksums.yaml
ADDED
@@ -0,0 +1,7 @@
|
|
1
|
+
---
|
2
|
+
SHA256:
|
3
|
+
metadata.gz: e05bf4fc6e133c3ae6c6ded26adc3b11647bc5258f714307011779b05f5a4bd8
|
4
|
+
data.tar.gz: 2968b9196978abcd0d3b06a7871b9131cd30bc8075b95587596d084732468373
|
5
|
+
SHA512:
|
6
|
+
metadata.gz: 4060048796877c10e0a96270bd6f44b5a389b14eccf112e88da4ba680a86eda1bbf50b4d8cbd2ae3f4854ef12062a9984c1f576f8cd22bd56eb6e81105515b6f
|
7
|
+
data.tar.gz: 1b41773116b9166343b98616ac0d51f6aa4e39e5c1d66809cbe98cd56da48bd48add8e0034312bc3bdf81a0bde83e2e33c256d653fa18434cff1b464678a1e11
|
data/.gitignore
ADDED
data/.rspec
ADDED
data/.travis.yml
ADDED
data/CODE_OF_CONDUCT.md
ADDED
@@ -0,0 +1,74 @@
|
|
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 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 joel@electricfeel.com. 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/
|
data/Gemfile
ADDED
data/Gemfile.lock
ADDED
@@ -0,0 +1,35 @@
|
|
1
|
+
PATH
|
2
|
+
remote: .
|
3
|
+
specs:
|
4
|
+
sane_patch (0.1.0)
|
5
|
+
|
6
|
+
GEM
|
7
|
+
remote: https://rubygems.org/
|
8
|
+
specs:
|
9
|
+
diff-lcs (1.3)
|
10
|
+
rake (10.5.0)
|
11
|
+
rspec (3.7.0)
|
12
|
+
rspec-core (~> 3.7.0)
|
13
|
+
rspec-expectations (~> 3.7.0)
|
14
|
+
rspec-mocks (~> 3.7.0)
|
15
|
+
rspec-core (3.7.0)
|
16
|
+
rspec-support (~> 3.7.0)
|
17
|
+
rspec-expectations (3.7.0)
|
18
|
+
diff-lcs (>= 1.2.0, < 2.0)
|
19
|
+
rspec-support (~> 3.7.0)
|
20
|
+
rspec-mocks (3.7.0)
|
21
|
+
diff-lcs (>= 1.2.0, < 2.0)
|
22
|
+
rspec-support (~> 3.7.0)
|
23
|
+
rspec-support (3.7.0)
|
24
|
+
|
25
|
+
PLATFORMS
|
26
|
+
ruby
|
27
|
+
|
28
|
+
DEPENDENCIES
|
29
|
+
bundler (~> 2.0)
|
30
|
+
rake (~> 10.0)
|
31
|
+
rspec (~> 3.0)
|
32
|
+
sane_patch!
|
33
|
+
|
34
|
+
BUNDLED WITH
|
35
|
+
2.0.1
|
data/LICENSE.txt
ADDED
@@ -0,0 +1,21 @@
|
|
1
|
+
The MIT License (MIT)
|
2
|
+
|
3
|
+
Copyright (c) 2019 Joel Ambass
|
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.
|
data/README.md
ADDED
@@ -0,0 +1,115 @@
|
|
1
|
+
# SanePatch
|
2
|
+
|
3
|
+
SanePatch is a simple and non intrusive helper that aims to make monkey patching a little bit safer.
|
4
|
+
|
5
|
+
It achieves this by only applying your patches to a specific version of a gem and raising a exception if the gem version changed. This means that you will always double check that your patches still work after upgrading gems. No surprises anymore!
|
6
|
+
|
7
|
+
## But wait.. Isn't monkey patching bad?
|
8
|
+
|
9
|
+
As with many things in life there is no pure good or bad. Monkey patching can be dangerous in certain situations and should be avoided sometimes but there are reasons to use it.
|
10
|
+
|
11
|
+
Good reasons to monkey patch a gem could be:
|
12
|
+
- Fixing a small bug in a broken gem until a new version of it is released.
|
13
|
+
- Performance optimizing a specific method of a gem that is used in a hot code path.
|
14
|
+
- Probably many more...
|
15
|
+
|
16
|
+
## Installation
|
17
|
+
|
18
|
+
Add this line to your application's Gemfile:
|
19
|
+
|
20
|
+
```ruby
|
21
|
+
gem 'sane_patch'
|
22
|
+
```
|
23
|
+
|
24
|
+
And then execute:
|
25
|
+
|
26
|
+
$ bundle
|
27
|
+
|
28
|
+
## Usage
|
29
|
+
|
30
|
+
The usage of SanePatch is straight forward:
|
31
|
+
|
32
|
+
|
33
|
+
```ruby
|
34
|
+
SanePatch.patch('<gem name>', '<current gem version>') do
|
35
|
+
# Apply your patches here the same way as usual.
|
36
|
+
end
|
37
|
+
```
|
38
|
+
|
39
|
+
A more specific example:
|
40
|
+
|
41
|
+
```ruby
|
42
|
+
|
43
|
+
Greeter.greet # => 'Hello'
|
44
|
+
|
45
|
+
# Let's patch the `Greeter.greet` method to output 'Hello Folks'
|
46
|
+
module GreeterPatch
|
47
|
+
def greet
|
48
|
+
"#{super} Folks"
|
49
|
+
end
|
50
|
+
end
|
51
|
+
|
52
|
+
# We currently have version 1.1.0 of the greeter gem
|
53
|
+
SanePatch.patch('greeter', '1.1.0') do
|
54
|
+
Greeter.prepend(GreeterPatch)
|
55
|
+
end
|
56
|
+
|
57
|
+
Greeter.greet # => 'Hello Folk'
|
58
|
+
```
|
59
|
+
|
60
|
+
If somebody updates the gem version the patch will raise as soon as its code path is executed:
|
61
|
+
```
|
62
|
+
It looks like the greeter gem was upgraded. (RuntimeError)
|
63
|
+
There are patches in place that need to be verified.
|
64
|
+
Make sure that the patch at initializers/greeter_patch.rb:8 is still needed and working.
|
65
|
+
```
|
66
|
+
|
67
|
+
### Providing additional information
|
68
|
+
|
69
|
+
If you patch a known bug in a gem it might be useful to provide additional information why the patch is needed and when it can be removed.
|
70
|
+
|
71
|
+
```ruby
|
72
|
+
Greeter.silence # => nil
|
73
|
+
|
74
|
+
module GreeterPatch
|
75
|
+
def silence
|
76
|
+
''
|
77
|
+
end
|
78
|
+
end
|
79
|
+
|
80
|
+
details = <<-MSG
|
81
|
+
The `silence` method should output an empty string rather than nil.
|
82
|
+
This is a known issue and will be fixed in the next realase.
|
83
|
+
See: https://github.com/Jcambass/greeter/issues/45
|
84
|
+
MSG
|
85
|
+
|
86
|
+
SanePatch.patch('greeter', '1.1.0', details: details) do
|
87
|
+
Greeter.prepend(GreeterPatch)
|
88
|
+
end
|
89
|
+
|
90
|
+
Greeter.silence # => ''
|
91
|
+
```
|
92
|
+
|
93
|
+
The additionally provided details will also show up in the exception message.
|
94
|
+
|
95
|
+
```
|
96
|
+
It looks like the greeter gem was upgraded. (RuntimeError)
|
97
|
+
There are patches in place that need to be verified.
|
98
|
+
Make sure that the patch at initializers/greeter_patch.rb:8 is still needed and working.
|
99
|
+
Details:
|
100
|
+
The `silence` method should output an empty string rather than nil.
|
101
|
+
This is a known issue and will be fixed in the next realase.
|
102
|
+
See: https://github.com/Jcambass/greeter/issues/45
|
103
|
+
```
|
104
|
+
|
105
|
+
## Contributing
|
106
|
+
|
107
|
+
Bug reports and pull requests are welcome on GitHub at https://github.com/Jcambass/sane_patch. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
|
108
|
+
|
109
|
+
## License
|
110
|
+
|
111
|
+
The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
|
112
|
+
|
113
|
+
## Code of Conduct
|
114
|
+
|
115
|
+
Everyone interacting in the SanePatch project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/Jambass/sane_patch/blob/master/CODE_OF_CONDUCT.md).
|
data/Rakefile
ADDED
data/lib/sane_patch.rb
ADDED
@@ -0,0 +1,22 @@
|
|
1
|
+
require "sane_patch/version"
|
2
|
+
|
3
|
+
module SanePatch
|
4
|
+
def self.patch(gem_name, version, details: nil)
|
5
|
+
gem_spec = Gem.loaded_specs[gem_name]
|
6
|
+
patched_version = Gem::Version.new(version)
|
7
|
+
raise ArgumentError, "Can't patch unloaded gem #{gem_name}" unless gem_spec
|
8
|
+
|
9
|
+
if gem_spec.version == patched_version
|
10
|
+
yield
|
11
|
+
else
|
12
|
+
message = <<~ERROR
|
13
|
+
It looks like the #{gem_name} gem was upgraded.
|
14
|
+
There are patches in place that need to be verified.
|
15
|
+
Make sure that the patch at #{caller_locations.first} is still needed and working.
|
16
|
+
ERROR
|
17
|
+
message += "Details: \n #{details}" if details
|
18
|
+
|
19
|
+
raise message
|
20
|
+
end
|
21
|
+
end
|
22
|
+
end
|
data/sane_patch.gemspec
ADDED
@@ -0,0 +1,39 @@
|
|
1
|
+
|
2
|
+
lib = File.expand_path("../lib", __FILE__)
|
3
|
+
$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
|
4
|
+
require "sane_patch/version"
|
5
|
+
|
6
|
+
Gem::Specification.new do |spec|
|
7
|
+
spec.name = "sane_patch"
|
8
|
+
spec.version = SanePatch::VERSION
|
9
|
+
spec.authors = ["Joel Ambass"]
|
10
|
+
spec.email = ["hello@joel.am"]
|
11
|
+
|
12
|
+
spec.summary = %q{Making monkey patches sane again}
|
13
|
+
spec.description = %q{SanePatch will prevent gem upgrades from sillently breaking your monkey patches.}
|
14
|
+
spec.homepage = "https://github.com/Jcambass/sane_patch"
|
15
|
+
spec.license = "MIT"
|
16
|
+
|
17
|
+
# Prevent pushing this gem to RubyGems.org. To allow pushes either set the 'allowed_push_host'
|
18
|
+
# to allow pushing to a single host or delete this section to allow pushing to any host.
|
19
|
+
if spec.respond_to?(:metadata)
|
20
|
+
spec.metadata["homepage_uri"] = spec.homepage
|
21
|
+
spec.metadata["source_code_uri"] = "https://github.com/Jcambass/sane_patch"
|
22
|
+
else
|
23
|
+
raise "RubyGems 2.0 or newer is required to protect against " \
|
24
|
+
"public gem pushes."
|
25
|
+
end
|
26
|
+
|
27
|
+
# Specify which files should be added to the gem when it is released.
|
28
|
+
# The `git ls-files -z` loads the files in the RubyGem that have been added into git.
|
29
|
+
spec.files = Dir.chdir(File.expand_path('..', __FILE__)) do
|
30
|
+
`git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
|
31
|
+
end
|
32
|
+
spec.bindir = "exe"
|
33
|
+
spec.executables = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
|
34
|
+
spec.require_paths = ["lib"]
|
35
|
+
|
36
|
+
spec.add_development_dependency "bundler", "~> 2.0"
|
37
|
+
spec.add_development_dependency "rake", "~> 10.0"
|
38
|
+
spec.add_development_dependency "rspec", "~> 3.0"
|
39
|
+
end
|
metadata
ADDED
@@ -0,0 +1,100 @@
|
|
1
|
+
--- !ruby/object:Gem::Specification
|
2
|
+
name: sane_patch
|
3
|
+
version: !ruby/object:Gem::Version
|
4
|
+
version: 0.1.0
|
5
|
+
platform: ruby
|
6
|
+
authors:
|
7
|
+
- Joel Ambass
|
8
|
+
autorequire:
|
9
|
+
bindir: exe
|
10
|
+
cert_chain: []
|
11
|
+
date: 2019-05-23 00:00:00.000000000 Z
|
12
|
+
dependencies:
|
13
|
+
- !ruby/object:Gem::Dependency
|
14
|
+
name: bundler
|
15
|
+
requirement: !ruby/object:Gem::Requirement
|
16
|
+
requirements:
|
17
|
+
- - "~>"
|
18
|
+
- !ruby/object:Gem::Version
|
19
|
+
version: '2.0'
|
20
|
+
type: :development
|
21
|
+
prerelease: false
|
22
|
+
version_requirements: !ruby/object:Gem::Requirement
|
23
|
+
requirements:
|
24
|
+
- - "~>"
|
25
|
+
- !ruby/object:Gem::Version
|
26
|
+
version: '2.0'
|
27
|
+
- !ruby/object:Gem::Dependency
|
28
|
+
name: rake
|
29
|
+
requirement: !ruby/object:Gem::Requirement
|
30
|
+
requirements:
|
31
|
+
- - "~>"
|
32
|
+
- !ruby/object:Gem::Version
|
33
|
+
version: '10.0'
|
34
|
+
type: :development
|
35
|
+
prerelease: false
|
36
|
+
version_requirements: !ruby/object:Gem::Requirement
|
37
|
+
requirements:
|
38
|
+
- - "~>"
|
39
|
+
- !ruby/object:Gem::Version
|
40
|
+
version: '10.0'
|
41
|
+
- !ruby/object:Gem::Dependency
|
42
|
+
name: rspec
|
43
|
+
requirement: !ruby/object:Gem::Requirement
|
44
|
+
requirements:
|
45
|
+
- - "~>"
|
46
|
+
- !ruby/object:Gem::Version
|
47
|
+
version: '3.0'
|
48
|
+
type: :development
|
49
|
+
prerelease: false
|
50
|
+
version_requirements: !ruby/object:Gem::Requirement
|
51
|
+
requirements:
|
52
|
+
- - "~>"
|
53
|
+
- !ruby/object:Gem::Version
|
54
|
+
version: '3.0'
|
55
|
+
description: SanePatch will prevent gem upgrades from sillently breaking your monkey
|
56
|
+
patches.
|
57
|
+
email:
|
58
|
+
- hello@joel.am
|
59
|
+
executables: []
|
60
|
+
extensions: []
|
61
|
+
extra_rdoc_files: []
|
62
|
+
files:
|
63
|
+
- ".gitignore"
|
64
|
+
- ".rspec"
|
65
|
+
- ".travis.yml"
|
66
|
+
- CODE_OF_CONDUCT.md
|
67
|
+
- Gemfile
|
68
|
+
- Gemfile.lock
|
69
|
+
- LICENSE.txt
|
70
|
+
- README.md
|
71
|
+
- Rakefile
|
72
|
+
- lib/sane_patch.rb
|
73
|
+
- lib/sane_patch/version.rb
|
74
|
+
- sane_patch.gemspec
|
75
|
+
homepage: https://github.com/Jcambass/sane_patch
|
76
|
+
licenses:
|
77
|
+
- MIT
|
78
|
+
metadata:
|
79
|
+
homepage_uri: https://github.com/Jcambass/sane_patch
|
80
|
+
source_code_uri: https://github.com/Jcambass/sane_patch
|
81
|
+
post_install_message:
|
82
|
+
rdoc_options: []
|
83
|
+
require_paths:
|
84
|
+
- lib
|
85
|
+
required_ruby_version: !ruby/object:Gem::Requirement
|
86
|
+
requirements:
|
87
|
+
- - ">="
|
88
|
+
- !ruby/object:Gem::Version
|
89
|
+
version: '0'
|
90
|
+
required_rubygems_version: !ruby/object:Gem::Requirement
|
91
|
+
requirements:
|
92
|
+
- - ">="
|
93
|
+
- !ruby/object:Gem::Version
|
94
|
+
version: '0'
|
95
|
+
requirements: []
|
96
|
+
rubygems_version: 3.0.3
|
97
|
+
signing_key:
|
98
|
+
specification_version: 4
|
99
|
+
summary: Making monkey patches sane again
|
100
|
+
test_files: []
|