rubysmith 0.16.1 → 1.2.0

data/lib/rubysmith/cli/configuration/enhancers/version.rb

@@ -1,26 +0,0 @@
-# frozen_string_literal: true
-
-require "refinements/structs"
-
-module Rubysmith
-  module CLI
-    module Configuration
-      module Enhancers
-        # Adds this gem's version to content.
-        class Version
-          using Refinements::Structs
-
-          def initialize version = Identity::VERSION_LABEL
-            @version = version
-          end
-
-          def call(content) = content.merge(version: version)
-
-          private
-
-          attr_reader :version
-        end
-      end
-    end
-  end
-end

data/lib/rubysmith/cli/configuration/loader.rb

@@ -1,46 +0,0 @@
-# frozen_string_literal: true
-
-require "pathname"
-require "refinements/hashes"
-require "refinements/structs"
-require "runcom"
-require "yaml"
-
-module Rubysmith
-  module CLI
-    module Configuration
-      # Represents the fully assembled Command Line Interface (CLI) configuration.
-      class Loader
-        using Refinements::Hashes
-        using Refinements::Structs
-
-        DEFAULTS = YAML.load_file(Pathname(__dir__).join("defaults.yml")).freeze
-        CLIENT = Runcom::Config.new "#{Identity::NAME}/configuration.yml", defaults: DEFAULTS
-
-        ENHANCERS = [
-          Enhancers::GitHubUser.new,
-          Enhancers::CurrentTime.new,
-          Enhancers::Version.new
-        ].freeze
-
-        def self.call(...) = new(...).call
-
-        def self.with_defaults = new(client: DEFAULTS, enhancers: [])
-
-        def initialize content: Content.new, client: CLIENT, enhancers: ENHANCERS
-          @content = content
-          @client = client
-          @enhancers = enhancers
-        end
-
-        def call = enhancers.reduce(preload_content) { |preload, enhancer| enhancer.call preload }
-
-        private
-
-        attr_reader :content, :client, :enhancers
-
-        def preload_content = content.merge(**client.to_h.flatten_keys)
-      end
-    end
-  end
-end

data/lib/rubysmith/cli/parsers/assembler.rb

@@ -1,32 +0,0 @@
-# frozen_string_literal: true
-
-module Rubysmith
-  module CLI
-    module Parsers
-      # Assembles and parses all Command Line Interface (CLI) options.
-      class Assembler
-        SECTIONS = [Core, Build].freeze # Order is important.
-
-        def initialize sections: SECTIONS, client: CLIENT, container: Container
-          @sections = sections
-          @client = client
-          @container = container
-        end
-
-        def call arguments = []
-          sections.each { |parser| parser.call client: client }
-          client.parse! arguments
-          configuration
-        end
-
-        def to_s = client.to_s
-
-        private
-
-        attr_reader :sections, :client, :container
-
-        def configuration = container[__method__]
-      end
-    end
-  end
-end

data/lib/rubysmith/cli/parsers.rb

@@ -1,11 +0,0 @@
-# frozen_string_literal: true
-
-require "optparse"
-
-module Rubysmith
-  module CLI
-    module Parsers
-      CLIENT = OptionParser.new nil, 40, "  "
-    end
-  end
-end

data/lib/rubysmith/identity.rb

@@ -1,11 +0,0 @@
-# frozen_string_literal: true
-
-module Rubysmith
-  module Identity
-    NAME = "rubysmith"
-    LABEL = "Rubysmith"
-    VERSION = "0.16.1"
-    VERSION_LABEL = "#{LABEL} #{VERSION}".freeze
-    SUMMARY = "A command line interface for smithing Ruby projects."
-  end
-end

data/lib/rubysmith/templates/%project_name%/CHANGES.adoc.erb

@@ -1,5 +0,0 @@
-= Changes
-
-== 0.1.0 (<%= configuration.now.strftime "%Y-%m-%d" %>)
-
-* Added initial implementation.

data/lib/rubysmith/templates/%project_name%/CHANGES.md.erb

@@ -1,5 +0,0 @@
-# Changes
-
-## 0.1.0 (<%= configuration.now.strftime "%Y-%m-%d" %>)
-
-- Added initial implementation.

data/lib/rubysmith/templates/%project_name%/CODE_OF_CONDUCT.adoc.erb

@@ -1,114 +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 link:mailto:<%= configuration.author_email %>?subject=Conduct[<%=
-configuration.author_name %>].
-
-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
-link:https://www.contributor-covenant.org/version/2/0/code_of_conduct.html[Contributor Covenant,
-Version 2.0].
-
-Community Impact Guidelines were inspired by link:https://github.com/mozilla/diversity[Mozilla's
-code of conduct enforcement ladder].
-
-For answers to common questions about this code of conduct, see the
-link:https://www.contributor-covenant.org/faq[FAQ]. Translations are available
-link:https://www.contributor-covenant.org/translations[here].

data/lib/rubysmith/templates/%project_name%/CODE_OF_CONDUCT.md.erb

@@ -1,115 +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 [<%= configuration.author_name %>](mailto:<%= configuration.author_email
-%>?subject=Conduct).
-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, Version
-2.0](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](https://www.contributor-covenant.org/faq). Translations are available
-[here](https://www.contributor-covenant.org/translations).
-

data/lib/rubysmith/templates/%project_name%/CONTRIBUTING.adoc.erb

@@ -1,22 +0,0 @@
-= Contributing
-
-Thanks for taking an interest in this open source project. Your support and involvement is greatly
-appreciated. The following details what you need to know in order to contribute.
-
-== Code
-
-. Read the project link:README.adoc[README] before starting.
-. Fork and clone the `master` branch of this repository locally.
-. Ensure there are no setup, usage, and/or test issues.
-. Add tests for new functionality and ensure they pass.
-. Submit a pull request, follow the instructions provided, and ensure the build passes.
-
-== Issues
-
-Submit an issue via the GitHub Issues tab (assuming one does not already exist) and follow the
-instructions provided.
-
-== Feedback
-
-* Expect a response within one to three business days.
-* Changes, alternatives, and/or improvements may be suggested upon review.

data/lib/rubysmith/templates/%project_name%/CONTRIBUTING.md.erb

@@ -1,22 +0,0 @@
-# Contributing
-
-Thanks for taking an interest in this open source project. Your support and involvement is greatly
-appreciated. The following details what you need to know in order to contribute.
-
-## Code
-
-1. Read the project README before starting.
-1. Fork and clone the `master` branch of this repository locally.
-1. Ensure there are no local setup, usage, and/or test issues.
-1. Add tests for new functionality and ensure they pass.
-1. Submit a pull request, follow the instructions provided, and ensure the build passes.
-
-## Issues
-
-- Submit an issue via the GitHub Issues tab (assuming one does not already exist) and follow the
-  instructions provided.
-
-## Feedback
-
-- Expect a response within one to three business days.
-- Changes, alternatives, and/or improvements may be suggested upon review.