activesupport-logger 2.0.3 → 3.0.0
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 +167 -3
- data/LICENSE.md +10 -0
- data/README.md +447 -181
- data/lib/active_support/logger.rb +4 -4
- data/lib/activesupport/isolated_execution_state.rb +19 -3
- data/lib/activesupport/logger/version.rb +4 -8
- data/lib/activesupport/logger.rb +7 -2
- data/lib/activesupport/logger_silence.rb +0 -0
- data/lib/activesupport/logger_thread_safe_level.rb +0 -0
- data/lib/activesupport-logger.rb +7 -6
- data/sig/activesupport/logger.rbs +22 -0
- data.tar.gz.sig +0 -0
- metadata +236 -106
- metadata.gz.sig +0 -0
- data/CODE_OF_CONDUCT.md +0 -84
- data/CONTRIBUTING.md +0 -106
- data/LICENSE.txt +0 -22
- data/SECURITY.md +0 -13
data/CONTRIBUTING.md
DELETED
|
@@ -1,106 +0,0 @@
|
|
|
1
|
-
## Contributing
|
|
2
|
-
|
|
3
|
-
Bug reports and pull requests are welcome on GitHub at [https://github.com/pboling/activesupport-logger][🚎src-main]
|
|
4
|
-
. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to
|
|
5
|
-
the [code of conduct][🤝conduct].
|
|
6
|
-
|
|
7
|
-
To submit a patch, please fork the project and create a patch with tests.
|
|
8
|
-
Once you're happy with it send a pull request.
|
|
9
|
-
|
|
10
|
-
## You can help!
|
|
11
|
-
|
|
12
|
-
Take a look at the `reek` list which is the file called `REEK` and find something to improve.
|
|
13
|
-
|
|
14
|
-
Simply follow these instructions:
|
|
15
|
-
|
|
16
|
-
1. Fork the repository
|
|
17
|
-
2. Create your feature branch (`git checkout -b my-new-feature`)
|
|
18
|
-
3. Make some fixes.
|
|
19
|
-
4. Commit your changes (`git commit -am 'Added some feature'`)
|
|
20
|
-
5. Push to the branch (`git push origin my-new-feature`)
|
|
21
|
-
6. Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
|
|
22
|
-
7. Create new Pull Request.
|
|
23
|
-
|
|
24
|
-
## Contributors
|
|
25
|
-
|
|
26
|
-
Your picture could be here!
|
|
27
|
-
|
|
28
|
-
[![Contributors][🖐contributors-img]][🖐contributors]
|
|
29
|
-
|
|
30
|
-
Made with [contributors-img][🖐contrib-rocks].
|
|
31
|
-
|
|
32
|
-
## The Reek List
|
|
33
|
-
|
|
34
|
-
To refresh the `reek` list:
|
|
35
|
-
|
|
36
|
-
```bash
|
|
37
|
-
bundle exec reek > REEK
|
|
38
|
-
```
|
|
39
|
-
|
|
40
|
-
## Appraisal
|
|
41
|
-
|
|
42
|
-
### Generate a new set of Appraisal gemfiles:
|
|
43
|
-
|
|
44
|
-
```bash
|
|
45
|
-
BUNDLE_GEMFILE=Appraisal.root.gemfile appraisal update
|
|
46
|
-
```
|
|
47
|
-
|
|
48
|
-
## Run Tests
|
|
49
|
-
|
|
50
|
-
```bash
|
|
51
|
-
bundle exec rake test
|
|
52
|
-
```
|
|
53
|
-
|
|
54
|
-
## Lint It
|
|
55
|
-
|
|
56
|
-
Run all the default tasks, which includes running the gradually autocorrecting linter, `rubocop-gradual`.
|
|
57
|
-
|
|
58
|
-
```bash
|
|
59
|
-
bundle exec rake
|
|
60
|
-
```
|
|
61
|
-
|
|
62
|
-
Or just run the linter.
|
|
63
|
-
```bash
|
|
64
|
-
bundle exec rubocop_gradual:autocorrect
|
|
65
|
-
```
|
|
66
|
-
|
|
67
|
-
## Release
|
|
68
|
-
|
|
69
|
-
### One-time, Per-developer, Setup
|
|
70
|
-
|
|
71
|
-
**IMPORTANT**: Your public key for signing gems will need to be picked up by the line in the
|
|
72
|
-
`gemspec` defining the `spec.cert_chain` (check the relevant ENV variables there),
|
|
73
|
-
in order to sign the new release.
|
|
74
|
-
See: [RubyGems Security Guide][🔒️rubygems-security-guide]
|
|
75
|
-
|
|
76
|
-
### To release a new version:
|
|
77
|
-
|
|
78
|
-
1. Run `bin/setup && bin/rake` as a tests, coverage, & linting sanity check
|
|
79
|
-
2. Update the version number in `version.rb`
|
|
80
|
-
3. Run `bin/setup && bin/rake` again as a secondary check, and to update `Gemfile.lock`
|
|
81
|
-
4. Run `git commit -am "🔖 Prepare release v<VERSION>"` to commit the changes
|
|
82
|
-
5. Run `git push` to trigger the final CI pipeline before release, & merge PRs
|
|
83
|
-
- NOTE: Remember to [check the build][🧪build]!
|
|
84
|
-
6. Run `export GIT_TRUNK_BRANCH_NAME="$(git remote show origin | grep 'HEAD branch' | cut -d ' ' -f5)" && echo $GIT_TRUNK_BRANCH_NAME`
|
|
85
|
-
7. Run `git checkout $GIT_TRUNK_BRANCH_NAME`
|
|
86
|
-
8. Run `git pull origin $GIT_TRUNK_BRANCH_NAME` to ensure you will release the latest trunk code
|
|
87
|
-
9. Set `SOURCE_DATE_EPOCH` so `rake build` and `rake release` use same timestamp, and generate same checksums
|
|
88
|
-
- Run `export SOURCE_DATE_EPOCH=$EPOCHSECONDS && echo $SOURCE_DATE_EPOCH`
|
|
89
|
-
- If the echo above has no output, then it didn't work.
|
|
90
|
-
- Note that you'll need the `zsh/datetime` module, if running `zsh`.
|
|
91
|
-
- In `bash` you can use `date +%s` instead, i.e. `export SOURCE_DATE_EPOCH=$(date +%s) && echo $SOURCE_DATE_EPOCH`
|
|
92
|
-
10. Run `bundle exec rake build`
|
|
93
|
-
11. Run `bin/checksums` (more [context][🔒️rubygems-checksums-pr]) to create SHA-256 and SHA-512 checksums
|
|
94
|
-
- Checksums will be committed automatically by the script, but not pushed
|
|
95
|
-
12. Run `bundle exec rake release` which will create a git tag for the version,
|
|
96
|
-
push git commits and tags, and push the `.gem` file to [rubygems.org][💎rubygems]
|
|
97
|
-
|
|
98
|
-
[🧪build]: https://github.com/pboling/activesupport-logger/actions
|
|
99
|
-
[🤝conduct]: https://github.com/pboling/activesupport-logger/blob/main/CODE_OF_CONDUCT.md
|
|
100
|
-
[🖐contrib-rocks]: https://contrib.rocks
|
|
101
|
-
[🖐contributors]: https://github.com/pboling/activesupport-logger/graphs/contributors
|
|
102
|
-
[🖐contributors-img]: https://contrib.rocks/image?repo=pboling/activesupport-logger
|
|
103
|
-
[💎rubygems]: https://rubygems.org
|
|
104
|
-
[🔒️rubygems-security-guide]: https://guides.rubygems.org/security/#building-gems
|
|
105
|
-
[🔒️rubygems-checksums-pr]: https://github.com/rubygems/guides/pull/325
|
|
106
|
-
[🚎src-main]: https://github.com/pboling/activesupport-logger
|
data/LICENSE.txt
DELETED
|
@@ -1,22 +0,0 @@
|
|
|
1
|
-
The MIT License (MIT)
|
|
2
|
-
|
|
3
|
-
Copyright (c) David Heinemeier Hansson
|
|
4
|
-
Copyright (c) 2024 Peter Boling
|
|
5
|
-
|
|
6
|
-
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
7
|
-
of this software and associated documentation files (the "Software"), to deal
|
|
8
|
-
in the Software without restriction, including without limitation the rights
|
|
9
|
-
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
10
|
-
copies of the Software, and to permit persons to whom the Software is
|
|
11
|
-
furnished to do so, subject to the following conditions:
|
|
12
|
-
|
|
13
|
-
The above copyright notice and this permission notice shall be included in
|
|
14
|
-
all copies or substantial portions of the Software.
|
|
15
|
-
|
|
16
|
-
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
17
|
-
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
18
|
-
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
19
|
-
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
20
|
-
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
21
|
-
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
|
|
22
|
-
THE SOFTWARE.
|
data/SECURITY.md
DELETED
|
@@ -1,13 +0,0 @@
|
|
|
1
|
-
# Security Policy
|
|
2
|
-
|
|
3
|
-
## Supported Versions
|
|
4
|
-
|
|
5
|
-
| Version | Supported |
|
|
6
|
-
|---------|-----------|
|
|
7
|
-
| 1.x | ✅ |
|
|
8
|
-
|
|
9
|
-
## Reporting a Vulnerability
|
|
10
|
-
|
|
11
|
-
Peter Boling is the primary maintainer of this gem. Please find a way
|
|
12
|
-
to [contact him directly](https://railsbling.com/contact) to report the issue. Include as much relevant information as
|
|
13
|
-
possible.
|