punchy_pp 0.0.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 808209467a2fcb9c60e695e881084e699769337e805954690c40c776146a86e5
+  data.tar.gz: d06ca534f20422316534dfcecc2e7b1f6ce51e60d3469a6b52b81ea02dcf427d
+SHA512:
+  metadata.gz: ffbe103d697878d16637a587297aa81ea3c6a80a0989589b2b8f0ac80d007be75b441e8e5ca33892e9ff1f70290057061167577befb01ef8700a378fc53439a8
+  data.tar.gz: f552143fae9f666bb1f70f011f09ccea4d6d0e5733cbdf4216ed08e50d4a54343e01cd363ae0e4dc3a7a76ca3a9d6975bf6f905653c0110c98a6265bec63fc0f

data/.standard.yml

@@ -0,0 +1,3 @@
+# For available configuration options, see:
+#   https://github.com/standardrb/standard
+ruby_version: 3.0

data/CHANGELOG.md

@@ -0,0 +1,5 @@
+## [Unreleased]
+
+## [0.1.0] - 2024-08-09
+
+- Initial release

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,84 @@
+# 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 F-3r@users.noreply.github.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/Guardfile

@@ -0,0 +1,42 @@
+# A sample Guardfile
+# More info at https://github.com/guard/guard#readme
+
+## Uncomment and set this to only include directories you want to watch
+# directories %w(app lib config test spec features) \
+#  .select{|d| Dir.exist?(d) ? d : UI.warning("Directory #{d} does not exist")}
+
+## Note: if you are using the `directories` clause above and you are not
+## watching the project directory ('.'), then you will want to move
+## the Guardfile to a watched dir and symlink it back, e.g.
+#
+#  $ mkdir config
+#  $ mv Guardfile config/
+#  $ ln -s config/Guardfile .
+#
+# and, you'll have to watch "config/Guardfile" instead of "Guardfile"
+
+guard :minitest do
+  # with Minitest::Unit
+  watch(%r{^test/(.*)/?test_(.*)\.rb$})
+  watch(%r{^lib/(.*/)?([^/]+)\.rb$}) { |m| "test/#{m[1]}test_#{m[2]}.rb" }
+  watch(%r{^test/test_helper\.rb$}) { "test" }
+
+  # with Minitest::Spec
+  # watch(%r{^spec/(.*)_spec\.rb$})
+  # watch(%r{^lib/(.+)\.rb$})         { |m| "spec/#{m[1]}_spec.rb" }
+  # watch(%r{^spec/spec_helper\.rb$}) { 'spec' }
+
+  # Rails 4
+  # watch(%r{^app/(.+)\.rb$})                               { |m| "test/#{m[1]}_test.rb" }
+  # watch(%r{^app/controllers/application_controller\.rb$}) { 'test/controllers' }
+  # watch(%r{^app/controllers/(.+)_controller\.rb$})        { |m| "test/integration/#{m[1]}_test.rb" }
+  # watch(%r{^app/views/(.+)_mailer/.+})                    { |m| "test/mailers/#{m[1]}_mailer_test.rb" }
+  # watch(%r{^lib/(.+)\.rb$})                               { |m| "test/lib/#{m[1]}_test.rb" }
+  # watch(%r{^test/.+_test\.rb$})
+  # watch(%r{^test/test_helper\.rb$}) { 'test' }
+
+  # Rails < 4
+  # watch(%r{^app/controllers/(.*)\.rb$}) { |m| "test/functional/#{m[1]}_test.rb" }
+  # watch(%r{^app/helpers/(.*)\.rb$})     { |m| "test/helpers/#{m[1]}_test.rb" }
+  # watch(%r{^app/models/(.*)\.rb$})      { |m| "test/unit/#{m[1]}_test.rb" }
+end

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2024 Fernando Martínez
+
+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/README.md

@@ -0,0 +1,34 @@
+# Punchy PP
+
+_A "whistle key finder" for you *puts*_
+
+
+## WAT?
+
+* Are you a [puts debuguerer](https://tenderlovemaking.com/2016/02/05/i-am-a-puts-debuggerer/)?
+* You tired of playing 'Where's Waldo' with your `puts`?
+* Sick of losing and forgeting where the heck you've _put_ them?
+* Or perhaps diying of boredom while scrolling through and endless river of uninteresting logs?
+
+If any of these is a **YES**, then, my dear friend, here I've got some well-deserved **punchy** for your puts'es
+
+## Usage
+
+`bundle add punchy_pp` or `gem install punchy_pp` and then include punchy_pp's printer method  `#ppp` in the top-level object, like so:
+
+> Note: `#ppp` stands for `Punchy Pretty Print`, or `Power pp` or _something_ pee pee :thinking: 
+
+```ruby
+require "punchy_pp" 
+include PunchyPP::Methods
+
+ppp "conspicuous"
+```
+
+And you'll get something like:
+
+![image of command line interface with very conspicuous strings](image.png)
+
+## Development, Contributing, License, CoC, etc, etc, etc
+
+MIT, Contributor Covenant Code of Conduct, etc, all the standard stuff Bundler happily made for me :grinning: Just reach out with an issue or PR

data/Rakefile

@@ -0,0 +1,10 @@
+# frozen_string_literal: true
+
+require "bundler/gem_tasks"
+require "minitest/test_task"
+
+Minitest::TestTask.create
+
+require "standard/rake"
+
+task default: %i[test standard]

data/lib/punchy_pp.rb

@@ -0,0 +1,105 @@
+# frozen_string_literal: true
+
+require "pp"
+
+module PunchyPP
+  VERSION = "0.0.0"
+
+  LINE_CONTINUATIION = "\e[94m···\e[0m  "
+  PATTERNS = {
+    white: "\e[30m\e[107m%s\e[0m",
+    green: "\e[30m\e[102m%s\e[0m",
+    magenta: "\e[97m\e[105m%s\e[0m",
+    yellow: "\e[30m\e[103m%s\e[0m",
+    blue: "\e[97m\e[104m%s\e[0m",
+    purple: "\e[97m\e[45m%s\e[0m",
+    cyan: "\e[30m\e[106m%s\e[0m",
+    red: "\e[97m\e[101m%s\e[0m"
+  }
+
+  PATTERNS.each do |color, pattern|
+    define_method color do |text|
+      pattern % text
+    end
+  end
+
+  COLOR_CYCLE = PATTERNS.keys.cycle
+
+  def cycle_color
+    @current_color = config[:color] || COLOR_CYCLE.next
+  end
+
+  def color
+    @current_color || cycle_color
+  end
+
+  def config
+    @config ||= {out: $stdout}
+  end
+
+  def config=(options)
+    @config = options
+  end
+
+  def paint(text)
+    send PunchyPP.color, text
+  end
+
+  def border(text = nil)
+    paint "  #{text.to_s.ljust(100)}"
+  end
+
+  def line(text = nil)
+    paint(" ") << "  %s" % text.to_s
+  end
+
+  def wrap_text(text, width = 80)
+    return text if text.size <= width
+
+    lines = []
+    current_line = ""
+
+    text.split(/\s/).each do |word|
+      if (current_line.size + word.size + 1) > width
+        lines << current_line
+        current_line = word
+      else
+        current_line += (current_line.empty? ? "" : " ") + word
+      end
+    end
+    lines << current_line unless current_line.empty?
+
+    lines[1..-1].each { |it| it.prepend LINE_CONTINUATIION } # standard:disable Style/SlicingWithRange
+    lines
+  end
+
+  def out(text)
+    PunchyPP.config[:out].puts text
+  end
+
+  def interesting_caller(callers)
+    callers.reject { |it| it.match __FILE__ }
+  end
+
+  def puts(*objects)
+    PunchyPP.cycle_color
+
+    title = caller(1..1).first.to_s
+    lines = objects
+      .map { |it| it.pretty_inspect }
+      .flat_map { |it| wrap_text it }
+
+    out border(title)
+    out line
+    out lines.map { |it| line it }
+    out line
+    out border " "
+  end
+
+  extend self
+  module Methods
+    def ppp(*objects)
+      PunchyPP.puts(*objects)
+    end
+  end
+end

data/sig/punchy_pp.rbs

@@ -0,0 +1,4 @@
+module PunchyPP
+  VERSION: String
+  # See the writing guide of rbs: https://github.com/ruby/rbs#guides
+end

metadata

@@ -0,0 +1,57 @@
+--- !ruby/object:Gem::Specification
+name: punchy_pp
+version: !ruby/object:Gem::Version
+  version: 0.0.0
+platform: ruby
+authors:
+- Fernando Martínez
+autorequire:
+bindir: exe
+cert_chain: []
+date: 2024-08-15 00:00:00.000000000 Z
+dependencies: []
+description: Are you a puts debuguerer too? Tired of playing 'Where's Waldo' with
+  your `puts`? Sick of losing and forgeting where the heck you've _put_ them in your
+  code? or diying of boredom while scrolling through and endless pit of uneventful
+  logs? If any of those is yes, then, my dear friend, I've got you some PunchyPP!
+email:
+- F-3r@users.noreply.github.com
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- ".standard.yml"
+- CHANGELOG.md
+- CODE_OF_CONDUCT.md
+- Guardfile
+- LICENSE.txt
+- README.md
+- Rakefile
+- image.png
+- lib/punchy_pp.rb
+- sig/punchy_pp.rbs
+homepage: https://github.com/sinaptia/punchy_pp
+licenses:
+- MIT
+metadata:
+  homepage_uri: https://github.com/sinaptia/punchy_pp
+post_install_message:
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: 2.5.0
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubygems_version: 3.5.3
+signing_key:
+specification_version: 4
+summary: The puts debugguerer's indispensable companion
+test_files: []