RubyGems - activesupport-logger - Versions diffs - 2.0.2 → 3.0.0 - Mend

activesupport-logger 2.0.2 → 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.

Files changed (20) hide show

checksums.yaml +4 -4
checksums.yaml.gz.sig +0 -0
data/CHANGELOG.md +175 -2
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 +228 -118
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/CODE_OF_CONDUCT.md DELETED Viewed

@@ -1,84 +0,0 @@
-# Contributor Covenant Code of Conduct
-## Our Pledge
-We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
-We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
-## Our Standards
-Examples of behavior that contributes to a positive environment for our community include:
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the overall community
-Examples of unacceptable behavior include:
-* The use of sexualized language or imagery, and sexual attention or
-  advances of any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email
-  address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-## Enforcement Responsibilities
-Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
-Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
-## Scope
-This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
-## Enforcement
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at peter.boling@gmail.com. All complaints will be reviewed and investigated promptly and fairly.
-All community leaders are obligated to respect the privacy and security of the reporter of any incident.
-## Enforcement Guidelines
-Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
-### 1. Correction
-**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
-**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
-### 2. Warning
-**Community Impact**: A violation through a single incident or series of actions.
-**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
-### 3. Temporary Ban
-**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
-**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
-### 4. Permanent Ban
-**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior,  harassment of an individual, or aggression toward or disparagement of classes of individuals.
-**Consequence**: A permanent ban from any sort of public interaction within the community.
-## Attribution
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
-available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
-Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
-[homepage]: https://www.contributor-covenant.org
-For answers to common questions about this code of conduct, see the FAQ at
-https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

data/CONTRIBUTING.md DELETED Viewed

@@ -1,106 +0,0 @@
-## Contributing
-Bug reports and pull requests are welcome on GitHub at [https://github.com/pboling/activesupport-logger][🚎src-main]
-. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to
-the [code of conduct][🤝conduct].
-To submit a patch, please fork the project and create a patch with tests.
-Once you're happy with it send a pull request.
-## You can help!
-Take a look at the `reek` list which is the file called `REEK` and find something to improve.
-Simply follow these instructions:
-1. Fork the repository
-2. Create your feature branch (`git checkout -b my-new-feature`)
-3. Make some fixes.
-4. Commit your changes (`git commit -am 'Added some feature'`)
-5. Push to the branch (`git push origin my-new-feature`)
-6. Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
-7. Create new Pull Request.
-## Contributors
-Your picture could be here!
-[![Contributors][🖐contributors-img]][🖐contributors]
-Made with [contributors-img][🖐contrib-rocks].
-## The Reek List
-To refresh the `reek` list:
-```bash
-bundle exec reek > REEK
-```
-## Appraisal
-### Generate a new set of Appraisal gemfiles:
-```bash
-BUNDLE_GEMFILE=Appraisal.root.gemfile appraisal update
-```
-## Run Tests
-```bash
-bundle exec rake test
-```
-## Lint It
-Run all the default tasks, which includes running the gradually autocorrecting linter, `rubocop-gradual`.
-```bash
-bundle exec rake
-```
-Or just run the linter.
-```bash
-bundle exec rubocop_gradual:autocorrect
-```
-## Release
-### One-time, Per-developer, Setup
-**IMPORTANT**: Your public key for signing gems will need to be picked up by the line in the
-`gemspec` defining the `spec.cert_chain` (check the relevant ENV variables there),
-in order to sign the new release.
-See: [RubyGems Security Guide][🔒️rubygems-security-guide]
-### To release a new version:
-1. Run `bin/setup && bin/rake` as a tests, coverage, & linting sanity check
-2. Update the version number in `version.rb`
-3. Run `bin/setup && bin/rake` again as a secondary check, and to update `Gemfile.lock`
-4. Run `git commit -am "🔖 Prepare release v<VERSION>"` to commit the changes
-5. Run `git push` to trigger the final CI pipeline before release, & merge PRs
-   - NOTE: Remember to [check the build][🧪build]!
-6. Run `export GIT_TRUNK_BRANCH_NAME="$(git remote show origin | grep 'HEAD branch' | cut -d ' ' -f5)" && echo $GIT_TRUNK_BRANCH_NAME`
-7. Run `git checkout $GIT_TRUNK_BRANCH_NAME`
-8. Run `git pull origin $GIT_TRUNK_BRANCH_NAME` to ensure you will release the latest trunk code
-9. Set `SOURCE_DATE_EPOCH` so `rake build` and `rake release` use same timestamp, and generate same checksums
-   - Run `export SOURCE_DATE_EPOCH=$EPOCHSECONDS && echo $SOURCE_DATE_EPOCH`
-   - If the echo above has no output, then it didn't work.
-   - Note that you'll need the `zsh/datetime` module, if running `zsh`.
-   - In `bash` you can use `date +%s` instead, i.e. `export SOURCE_DATE_EPOCH=$(date +%s) && echo $SOURCE_DATE_EPOCH`
-10. Run `bundle exec rake build`
-11. Run `bin/checksums` (more [context][🔒️rubygems-checksums-pr]) to create SHA-256 and SHA-512 checksums
-    - Checksums will be committed automatically by the script, but not pushed
-12. Run `bundle exec rake release` which will create a git tag for the version,
-    push git commits and tags, and push the `.gem` file to [rubygems.org][💎rubygems]
-[🧪build]: https://github.com/pboling/activesupport-logger/actions
-[🤝conduct]: https://github.com/pboling/activesupport-logger/blob/main/CODE_OF_CONDUCT.md
-[🖐contrib-rocks]: https://contrib.rocks
-[🖐contributors]: https://github.com/pboling/activesupport-logger/graphs/contributors
-[🖐contributors-img]: https://contrib.rocks/image?repo=pboling/activesupport-logger
-[💎rubygems]: https://rubygems.org
-[🔒️rubygems-security-guide]: https://guides.rubygems.org/security/#building-gems
-[🔒️rubygems-checksums-pr]: https://github.com/rubygems/guides/pull/325
-[🚎src-main]: https://github.com/pboling/activesupport-logger

data/LICENSE.txt DELETED Viewed

@@ -1,22 +0,0 @@
-The MIT License (MIT)
-Copyright (c) David Heinemeier Hansson
-Copyright (c) 2024 Peter Boling
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.

data/SECURITY.md DELETED Viewed

@@ -1,13 +0,0 @@
-# Security Policy
-## Supported Versions
-| Version | Supported |
-|---------|-----------|
-| 1.x     | ✅         |
-## Reporting a Vulnerability
-Peter Boling is the primary maintainer of this gem. Please find a way
-to [contact him directly](https://railsbling.com/contact) to report the issue. Include as much relevant information as
-possible.