Say

Say gives you the API and the output style you already know and love from ActiveRecord::Migration#say... anywhere! Plus a few extra goodies for long-running processes like incremental progress indicators and remaining time estimation.

Installation

Add this line to your application's Gemfile:

gem "say", github: "pdobb/say"

And then execute:

bundle

Compatibility

Tested MRI Ruby Versions:

3.2
3.3
3.4

For Ruby 2.7 support, install say gem version 0.5.2.

gem "say", github: "pdobb/say", "0.5.2"

For Ruby 3.1 support, install say gem version 0.6.0.

gem "say", github: "pdobb/say", "0.6.0"

Say has no other dependencies.

Usage

`include Say`

Typical usage is to include Say in your object and then call the say method as needed.

When called with a block, say will output both Start and Finish banners, while still returning the result of the block. When called without a block, say will output a string of the specified type (defaults to :success).

require "say"

class IncludeProcessor
  include Say

  def run
    say("IncludeProcessor") {
      say("Successfully did the thing!")
      say
      say("Debug details about this ...", :debug)
      say("Info about stuff ...", :info)
      say("Maybe look into this thing ...", :warn)
      say("Failed to do a thing ...", :error)

      "The Result!"
    }
  end
end

result = IncludeProcessor.new.run
= IncludeProcessor =============================================================
 -> Successfully did the thing!
 ...
 >> Debug details about this ...
 -- Info about stuff ...
 !¡ Maybe look into this thing ...
 ** Failed to do a thing ...
= Done (0.0001s) ===============================================================

result  # => "The Result!"

`Say.<method>`

For quick-access usage, you can just call Say.<method> without needing to include Say.

require "say"

class DirectAccessProcessor
  def run
    Say.("DirectAccessProcessor") {
      Say.("Successfully did the thing!")
      Say.() # Or: Say.call
      Say.("Debug details about this ...", :debug)
      Say.("Info about stuff ...", :info)
      Say.("Maybe look into this thing ...", :warn)
      Say.("Failed to do a thing ...", :error)

      "The Result!"
    }
  end
end

result = DirectAccessProcessor.new.run
= DirectAccessProcessor ========================================================
 -> Successfully did the thing!
 ...
 >> Debug details about this ...
 -- Info about stuff ...
 !¡ Maybe look into this thing ...
 ** Failed to do a thing ...
= Done (0.0001s) ===============================================================

result  # => "The Result!"

Say Types

When using Say.(<message>, <type>), the available types and output representations are:

Type	Output Prefix
`:debug`	`" >> "`
`:error`	`" ** "`
`:info`	`" -- "`
`:success`	`" -> "`
`:warn`	`" !¡ "`

Say.("TEST", :debug)   # => " >> TEST"
Say.("TEST", :error)   # => " ** TEST"
Say.("TEST", :info)    # => " -- TEST"
Say.("TEST", :success) # => " -> TEST"
Say.("TEST", :warn)    # => " !¡ TEST"

The default type is :success.

Say.("TEST")  # => " -> TEST"

`Say.<type>` Methods

Single-argument alternatives for each of the <type> calls in the previous section:

Say.debug("TEST")   # => " >> TEST"
Say.error("TEST")   # => " ** TEST"
Say.info("TEST")    # => " -- TEST"
Say.success("TEST") # => " -> TEST"
Say.warn("TEST")    # => " !¡ TEST"

`Say.section`

Use Say.section for 3-line banners to really visually split up your output into major sections.

Say.section
================================================================================
================================================================================
================================================================================

Say.section("TEST")
================================================================================
= TEST =========================================================================
================================================================================

Say.section("TEST", columns: 0)
========
= TEST =
========

Justifiers

The various banner-producing methods also support left/center/right justification. Just pass in e.g. justify: :left, justify: :center, or justify: :right. The default, if nothing is supplied, is justify: :left.

# Block

Say.("Hello, World!") { Say.("Huzzah!") }
= Hello, World! ================================================================
 -> Huzzah!
= Done (0.0000s) ===============================================================

Say.("Hello, World!", justify: :left) { Say.("Huzzah!") }
= Hello, World! ================================================================
 -> Huzzah!
= Done (0.0000s) ===============================================================

Say.("Hello, World!", justify: :center) { Say.("Huzzah!") }
================================= Hello, World! ================================
 -> Huzzah!
================================ Done (0.0000s) ================================

Say.("Hello, World!", justify: :right) { Say.("Huzzah!") }
================================================================ Hello, World! =
 -> Huzzah!
=============================================================== Done (0.0000s) =

# Banner

Say.banner("TEST")
= TEST =========================================================================

Say.banner("TEST", justify: :left)
= TEST =========================================================================

Say.banner("TEST", justify: :center)
===================================== TEST =====================================

Say.banner("TEST", justify: :right)
========================================================================= TEST =

# Header

Say.header("TEST")
= TEST =========================================================================

Say.header("TEST", justify: :left)
= TEST =========================================================================

Say.header("TEST", justify: :center)
===================================== TEST =====================================

Say.header("TEST", justify: :right)
========================================================================= TEST =

# Footer

Say.footer
= Done =========================================================================

Say.footer(justify: :left)
= Done =========================================================================

Say.footer(justify: :center)
===================================== Done =====================================

Say.footer(justify: :right)
========================================================================= Done =

# Section

Say.section("TEST")
================================================================================
= TEST =========================================================================
================================================================================

Say.section("TEST", justify: :left)
================================================================================
= TEST =========================================================================
================================================================================

Say.section("TEST", justify: :center)
================================================================================
===================================== TEST =====================================
================================================================================

Say.section("TEST", justify: :right)
================================================================================
========================================================================= TEST =
================================================================================

NOTE: The "line" methods will ignore justification attempts as there is no built in concept of columns for these.

Say.("TEST", justify: :right)  # `justify: :right` is ignored.
 -> TEST

Advanced Usage

All of the above examples are using the default interpolation template accessed via the Say.<method> methods. For advanced usage, one may access the Say::InterpolationTemplate directly and either use the predefined templates or specify their own.

Predefined interpolation templates

# :hr
interpolation_template = Say::InterpolationTemplate::Builder.hr

interpolation_template.inspect                            # => "['=', ...]{}['=', ...]"
interpolation_template.interpolate                        # => "=="
interpolation_template.left_justify(length: 20)           # => "===================="

# :title (the default template, if none is specified)
interpolation_template = Say::InterpolationTemplate::Builder.title

interpolation_template.inspect                            # => ['=', ...] {} ['=', ...]
interpolation_template.interpolate("TEST")                # => "= TEST ="
interpolation_template.left_justify("TEST", length: 20)   # => "= TEST ============="
interpolation_template.center_justify("TEST", length: 20) # => "======= TEST ======="
interpolation_template.right_justify("TEST", length: 20)  # => "============= TEST ="

# :wtf
interpolation_template = Say::InterpolationTemplate::Builder.wtf

interpolation_template.inspect                            # => "['?', ...] {} ['?', ...]"
interpolation_template.interpolate("TEST")                # => "? TEST ?"
interpolation_template.left_justify("TEST", length: 20)   # => "? TEST ?????????????"
interpolation_template.center_justify("TEST", length: 20) # => "??????? TEST ???????"
interpolation_template.right_justify("TEST", length: 20)  # => "????????????? TEST ?"

Custom interpolation templates

# Example 1
interpolation_template =
  Say::InterpolationTemplate.new(left_bookend: "╰(⇀︿⇀)つ-]═", left_fill: "-", right_fill: "-")

interpolation_template.inspect
# => "╰(⇀︿⇀)つ-]═['-', ...]{}['-', ...]"

interpolation_template.interpolate("TEST")
# => "╰(⇀︿⇀)つ-]═-TEST-"

interpolation_template.left_justify("TEST", length: 40)
# => "╰(⇀︿⇀)つ-]═-TEST-------------------------"

interpolation_template.center_justify("TEST", length: 40)
# => "╰(⇀︿⇀)つ-]═--------TEST------------------"

interpolation_template.right_justify("TEST", length: 40)
# => "╰(⇀︿⇀)つ-]═-------------------------TEST-"


# Example 2
interpolation_template =
  Say::InterpolationTemplate.new(
    left_bookend: "( •_•)O*¯",
    left_fill: "`·.·´",
    right_fill: "`·.·´",
    right_bookend: "¯°Q(•_• )")

interpolation_template.inspect
# => "( •_•)O*¯['`·.·´', ...]{}['`·.·´', ...]¯°Q(•_• )"

interpolation_template.interpolate("TEST")
# => "( •_•)O*¯`·.·´TEST`·.·´¯°Q(•_• )"

interpolation_template.left_justify("TEST")
# => "( •_•)O*¯`·.·´TEST`·.·´`·.·´`·.·´`·.·´`·.·´`·.·´`·.·´`·.·´`·.·´`·.·´`·.¯°Q(•_• )"

interpolation_template.center_justify("TEST")
# => "( •_•)O*¯`·.·´`·.·´`·.·´`·.·´`·.·`·.·´TEST`·.·´`·.·´`·.·´`·.·´`·.·´`·.·¯°Q(•_• )"

interpolation_template.right_justify("TEST")
# => "( •_•)O*¯`·.·´`·.·´`·.·´`·.·´`·.·´`·.·´`·.·´`·.·´`·.·´`·.`·.·´TEST`·.·´¯°Q(•_• )"

Progress Tracking

Use Say.progress to track long-running processing loops on a given interval. Set the interval to receive say updates only during on-interval ticks through the loop. The default interval is 1, meaning every loop is considered on-interval.

Simple

# The default interval is 1.
Say.progress do |interval|
  3.times do
    # Increment the interval's internal index by 1.
    interval.update

    interval.say("Test", :debug)
  end
end
= [20230604151646] Start (i=0) =================================================
[20230604151646]  >> Test (i=1)
[20230604151646]  >> Test (i=2)
[20230604151646]  >> Test (i=3)
= Done (0.0000s) ===============================================================

Advanced

Say.progress("Progress Tracking Test", interval: 3) do |interval|
  0.upto(6) do |index|
    # Set the interval's internal index to the current index. This may be safer.
    interval.update(index)

    # Only "say" for on-interval ticks through the loop.
    interval.say("Before Update Interval.", :debug)
    # Optionally use a block to time a segment.
    interval.say("Progress Interval Block.") do
      sleep(0.025) # Do the work here.

      # Always "say", regardless of interval, in the usual way: with `Say.call`.
      Say.("Interval-Agnostic Update. Index: #{index}", :info)
    end
    interval.say("After Update Interval.", :debug)
  end
end
= [20230604151646] Progress Tracking Test (i=0) ================================
 -- Interval-Agnostic Update. Index: 0
 -- Interval-Agnostic Update. Index: 1
 -- Interval-Agnostic Update. Index: 2
[20230604151646]  >> Before Update Interval. (i=3)
= [20230604151646] Progress Interval Block. (i=3) ==============================
 -- Interval-Agnostic Update. Index: 3
= Done (0.0261s) ===============================================================

[20230604151646]  >> After Update Interval. (i=3)
 -- Interval-Agnostic Update. Index: 4
 -- Interval-Agnostic Update. Index: 5
[20230604151647]  >> Before Update Interval. (i=6)
= [20230604151647] Progress Interval Block. (i=6) ==============================
 -- Interval-Agnostic Update. Index: 6
= Done (0.0261s) ===============================================================

[20230604151647]  >> After Update Interval. (i=6)
= Done (0.1828s) ===============================================================

Manual

Internally, calling say on a Say::Progress::Interval object uses Say.progress_line to output the given message and index indicator. You may do the same even without an Interval object.

# Given a message. (The default Type is :info.)
Say.progress_line("TEST", index: 3)
# => [20230604151647]  -- TEST (i=3)

Say.progress_line("TEST", :success, index: 3)
# => [20230604151647]  -> TEST (i=3)

# Given no message.
Say.progress_line(index: 3)
# => [20230604151647]  ... (i=3)

Namespace Pollution

If you choose to include Say then your class will gain the following instance methods:

say
say_banner
say_footer
say_header
say_line
say_progress
say_progress_line
say_section
say_with_block

... though you probably really only need say, and sometimes: say_progress and/or say_progress_line.

class WithInclude
  include Say
end

class WithoutInclude
end

added_class_methods = WithInclude.methods - WithoutInclude.methods
Say.("Class methods added by `include Say`: #{added_class_methods}")
 -- Class methods added by `include Say`: []

added_instance_methods = (WithInclude.new.methods - WithoutInclude.new.methods).sort!
Say.("Instance methods added by `include Say`: #{added_instance_methods}")
 -> Instance methods added by `include Say`: [:say, :say_banner, :say_footer, :say_header, :say_line, :say_progress, :say_progress_line, :say_section, :say_with_block]

Integration

iTerm2

The standardized nature of Say's logging methods lends itself well to highlighting output types using iTerm2's Text Highlighting Triggers. To set this up, go to Settings for iTerm2 -> Profiles -> Advanced -> Triggers section: "Edit" Button.

For more help, see iTerm's documentation on Triggers.

The regular expressions and HEX codes used in the screenshot are:

(?<=^ )->(?= )  # Text HEX: #0ae400  Background HEX: transparent
(?<=^ )>>(?= )  # Text HEX: #ff6500  Background HEX: transparent
(?<=^ )--(?= )  # Text HEX: #ffffff  Background HEX: #666666
(?<=^ )!¡(?= )  # Text HEX: #ffff00  Background HEX: transparent
.*\*{2,}.*      # Text HEX: #ffffff  Background HEX: #ff0000

Development

After checking out the repo, run bin/setup to install dependencies. Then, run rake test to run the tests. Or, run rake to run the tests plus linters as well as yard (to confirm proper YARD documentation practices). You can also run bin/console for an interactive prompt that will allow you to experiment.

To install this gem onto your local machine, run bundle exec rake install.

Testing

To test this gem:

rake

Linters

rubocop

reek

npx prettier . --check
npx prettier . --write

Releases

To release a new version of this gem to RubyGems:

Update the version number in version.rb
Update CHANGELOG.md
Run bundle to update Gemfile.lock with the latest version info
Commit the changes. e.g. Bump to vX.Y.Z
Run rake release, which will create a git tag for the version, push git commits and the created tag, and push the .gem file to rubygems.org.

Documentation

YARD documentation can be generated and viewed live:

Install YARD: gem install yard
Run the YARD server: yard server --reload
Open the live documentation site: open http://localhost:8808

While the YARD server is running, documentation in the live site will be auto-updated on source code save (and site reload).

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/pdobb/say. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the code of conduct.

License

The gem is available as open source under the terms of the MIT License.

Code of Conduct

Everyone interacting in the Say project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.

Name		Name	Last commit message	Last commit date
Latest commit History 76 Commits
.github/workflows		.github/workflows
bin		bin
lib		lib
rakelib		rakelib
screenshots		screenshots
test		test
.gitignore		.gitignore
.prettierignore		.prettierignore
.reek.yml		.reek.yml
.rubocop.yml		.rubocop.yml
CHANGELOG.md		CHANGELOG.md
CODE_OF_CONDUCT.md		CODE_OF_CONDUCT.md
Gemfile		Gemfile
Gemfile.lock		Gemfile.lock
LICENSE.txt		LICENSE.txt
README.md		README.md
Rakefile		Rakefile
say.gemspec		say.gemspec

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

Say

Installation

Compatibility

Usage

`include Say`

`Say.<method>`

Say Types

`Say.<type>` Methods

`Say.section`

Justifiers

Advanced Usage

Predefined interpolation templates

Custom interpolation templates

Progress Tracking

Simple

Advanced

Manual

Namespace Pollution

Integration

iTerm2

Development

Testing

Linters

Releases

Documentation

Contributing

License

Code of Conduct

About

Releases 9

Languages

License

pdobb/say

Folders and files

Latest commit

History

Repository files navigation

Say

Installation

Compatibility

Usage

include Say

Say.<method>

Say Types

Say.<type> Methods

Say.section

Justifiers

Advanced Usage

Predefined interpolation templates

Custom interpolation templates

Progress Tracking

Simple

Advanced

Manual

Namespace Pollution

Integration

iTerm2

Development

Testing

Linters

Releases

Documentation

Contributing

License

Code of Conduct

About

Resources

License

Code of conduct

Stars

Watchers

Forks

Releases 9

Languages

`include Say`

`Say.<method>`

`Say.<type>` Methods

`Say.section`