onboardable 1.2.0 → 1.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 5190ba93a0d09c427d6314bd1e7645ca8052406683fd9bc8f8ee90a7d0ba2386
-  data.tar.gz: 3aa3d7073ecba0ab36c136584a48c5296e40c98d80fdab15b95cf8de7d014040
+  metadata.gz: 85ade5264e7e019c70f76d1ad5ccf9713257e596baaae4495eeaaa575146af2e
+  data.tar.gz: 17fb50df5dc091e8f8c1326c2b28dea7657e5f97efcc94d4ba3ab34ea41e242b
 SHA512:
-  metadata.gz: 5b5248e51f51c217d8ddaeb2171b4a653bf291e1c02302701b1a02fae9175430ded3100e2e87e5f95514d9e1676cb159fc3c939f49a218f7f9b61cd9ba01b39d
-  data.tar.gz: 83a10458cd15031209a7ceeb7f8dec8a46de0c1af1b2328f8d142a41739c0983a62e4a11729761465f3a36dcdf0e9e3b90df20732de6d22d5a50cb91c48dc0ef
+  metadata.gz: ea96934ba19039ad48f297314d1021aa9be880cbd324da0d7575ecd351bb61563193099180cf43e2da051053ba2f2cce8df06bc260206e2796ee30b6f383e040
+  data.tar.gz: 35db141793dec0c56ddbd667ac8e1d1bacb33dfcb032a83ace5bcc712ab4f3010504f66b838ac7f0feddd422b87eb494f5b9c2064d15c221babedb17ac941088

data/CHANGELOG.md

@@ -2,6 +2,10 @@
 
 ## [Unreleased]
 
+## [1.2.1] - 2024-06-01
+
+- Added trusted publisher
+
 ## [1.2.0] - 2024-05-25
 
 - Added `#second_step?` method to check if the target step is the second step.

data/CODE_OF_CONDUCT.md

@@ -2,18 +2,25 @@
 
 ## 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 as members, contributors, and leaders pledge to participate 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.
+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:
+Examples of behavior that contributes to a positive environment for
+our community includes:
 
 * 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
+* 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:
@@ -24,61 +31,90 @@ Examples of unacceptable behavior include:
 * 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
+* Other conduct that 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 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.
+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.
+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 includes 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 skrynnyk.artem@coaxsoft.com. All complaints will be reviewed and investigated promptly and fairly.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported
+to the community leaders responsible for enforcement at skrynnyk.artem@coaxsoft.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.
+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:
+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.
+**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.
+**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.
+**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.
+**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.
+**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.
+**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.
+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).
+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.
+<https://www.contributor-covenant.org/faq>. Translations are available at <https://www.contributor-covenant.org/translations>.

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    onboardable (1.2.0)
+    onboardable (1.2.1)
 
 GEM
   remote: https://rubygems.org/
@@ -12,7 +12,7 @@ GEM
     json (2.7.2)
     language_server-protocol (3.17.0.3)
     parallel (1.24.0)
-    parser (3.3.1.0)
+    parser (3.3.2.0)
       ast (~> 2.4.1)
       racc
     racc (1.8.0)
@@ -34,7 +34,7 @@ GEM
       diff-lcs (>= 1.2.0, < 2.0)
       rspec-support (~> 3.13.0)
     rspec-support (3.13.1)
-    rubocop (1.64.0)
+    rubocop (1.64.1)
       json (~> 2.3)
       language_server-protocol (>= 3.17.0)
       parallel (~> 1.10)
@@ -81,11 +81,11 @@ DEPENDENCIES
   onboardable!
   rake (~> 13.2, >= 13.2.1)
   rspec (~> 3.13)
-  rubocop (~> 1.64)
+  rubocop (~> 1.64, >= 1.64.1)
   rubocop-performance (~> 1.21)
   rubocop-rake (~> 0.6.0)
   rubocop-rspec (~> 2.29, >= 2.29.2)
   simplecov (~> 0.22.0)
 
 BUNDLED WITH
-   2.5.10
+   2.5.11

data/README.md

@@ -18,7 +18,7 @@ Install the gem and add to the application's Gemfile by executing:
 bundle add onboardable
 ```
 
-If bundler is not being used to manage dependencies, install the gem by executing:
+If the bundler is not being used to manage dependencies, install the gem by executing:
 
 ```shell
 gem install onboardable
@@ -29,31 +29,31 @@ gem install onboardable
 First, ensure that the Onboardable gem is installed and properly set up in your
 project as per the installation guide provided earlier.
 
-### Basic Configuration
-
-   To incorporate an onboarding process into your Ruby User class, start by
-   including the Onboardable module to add onboarding functionality. Then,
-   define the onboarding steps with the has_onboarding method, detailing each
-   step with helpful tooltips and descriptions. Here's how you can set it up:
-
-   ```ruby
-   class User
-     include Onboardable
-
-     has_onboarding do
-       step 'welcome', message: 'Welcome to your new account!'
-       step 'account_setup', task: 'Create credentials'
-       step 'confirmation'
-       step_from ExternalStepProvider
-     end
-   end
-
-   class ExternalStepProvider
-     def self.to_onboarding_step
-       Onboardable::Step.new('external_step', info: 'This is an external step.')
-     end
-   end
-   ```
+### Defining Onboarding Steps
+
+To incorporate an onboarding process into your `User` class, start by
+including the `Onboardable` module to add onboarding functionality. Then,
+define the onboarding steps with the `has_onboarding` method, detailing each
+step with helpful tooltips and descriptions. Here's how you can set it up:
+
+```ruby
+class User
+  include Onboardable
+
+  has_onboarding do
+    step 'welcome', message: 'Welcome to your new account!'
+    step 'account_setup', task: 'Create credentials'
+    step 'confirmation'
+    step_from ExternalStepProvider
+  end
+end
+
+class ExternalStepProvider
+  def self.to_onboarding_step
+    Onboardable::Step.new 'external_step', info: 'This is an external step.'
+  end
+end
+```
 
 ### Using the Onboarding Steps
 
@@ -68,14 +68,28 @@ that allow step navigation and state verification:
 
 1. **Initialize Onboarding Process**
 
-   Instantiate the onboarding process when a user object is created.
-   This sets up the initial step based on the defined onboarding flow.
+   - Instantiate the onboarding process when a `User` object is created.
+     This sets up the initial step based on the defined onboarding flow.
 
    ```ruby
    onboarding = User.new.onboarding
    ```
 
-1. **Check order of steps**
+   - For a more detailed setup, use the `Onboardable::List::Builder` to
+     create a custom onboarding flow with specific steps and details.
+
+    ```ruby
+   builder = Onboardable::List::Builder.new
+
+   builder.create_step 'welcome', message: 'Welcome to your new account!'
+   builder.create_step 'account_setup', task: 'Create credentials'
+   builder.create_step 'confirmation'
+   builder.create_step_from ExternalStepProvider
+
+   onboarding = builder.build
+    ```
+
+1. **Check the order of steps**
 
    Determine the order of steps in the onboarding process to ensure
    that the sequence is correct and that the steps are defined as expected.
@@ -137,7 +151,7 @@ that allow step navigation and state verification:
 
    Retrieve details about the current step, which can include the name,
    custom data, and status, to display appropriate information or help
-   the user complete tasks associated with the step.
+   the user completes tasks associated with the step.
 
    ```ruby
    onboarding.current_step        # Current step details

data/lib/onboardable/list/builder.rb

@@ -31,18 +31,16 @@ module Onboardable
       #
       # @param klass [Class] The class to be converted to a step.
       # @return [Step] The converted step.
-      # @raise [UndefinedMethodError] If the conversion method is not defined for the class.
-      def create_step_from!(klass)
+      def create_step_from(klass)
         (Step.try_convert(klass) || undefined_method_error!(klass)).tap { |step| add_step(step) }
       end
-      alias step_from create_step_from!
+      alias step_from create_step_from
 
       # Constructs a new List object from the steps added to the builder.
       #
       # @param current_step_name [String, nil] The name of the step to mark as current in the built list. Can be nil.
       # @return [Base] A new List object initialized with the steps and the specified current step.
-      # @raise [EmptyStepsError] If no steps have been added to the builder.
-      def build!(current_step_name)
+      def build(current_step_name)
         Base.new(convert_to_steps!, convert_to_step!(current_step_name || current_step.name))
       end
 
@@ -53,12 +51,12 @@ module Onboardable
       # @param step [Step] The step to be added.
       # @return [Step] The added step.
       def add_step(step)
-        step.tap do
-          name = step.name
+        step.name.then do |name|
           warn_about_override(name) if steps.key?(name)
           steps[name] = step
-          self.current_step ||= step
         end
+
+        step.tap { self.current_step = step }
       end
 
       # Assigns a hash of steps to the builder.

data/lib/onboardable/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Onboardable
-  VERSION = '1.2.0'
+  VERSION = '1.2.1'
 end

data/lib/onboardable.rb

@@ -12,8 +12,8 @@ require_relative 'onboardable/version'
 module Onboardable
   # Initializes the Onboardable module when included in a class, extending it with class and instance methods.
   #
-  # @param klass [Module] the class including the Onboardable module
-  # @return [untyped]
+  # @param klass [Module] The class including the Onboardable module
+  # @return [untyped] The class including the Onboardable module.
   def self.included(klass)
     klass.extend ClassMethods
     klass.include InstanceMethods
@@ -23,15 +23,15 @@ module Onboardable
   module ClassMethods
     # Retrieves or initializes a ListBuilder for onboarding steps at the class level.
     #
-    # @return [List::Builder] the ListBuilder associated with the class
+    # @return [List::Builder] The ListBuilder associated with the class.
     def list_builder
       @list_builder ||= List::Builder.new
     end
 
     # Configures onboarding steps via a ListBuilder with a provided block.
     #
-    # @yield [List::Builder] executes block in the context of List::Builder
-    # @return [Step] the current step in the building process
+    # @yield [List::Builder] Executes block in the context of List::Builder.
+    # @return [Step] The current step in the building process.
     def list_builder=(&block)
       list_builder.instance_eval(&block)
     end
@@ -39,10 +39,10 @@ module Onboardable
 
     # Builds the onboarding list and optionally sets the current step.
     #
-    # @param current_step_name [String, nil] the name of the current step, if specified
-    # @return [List::Base] the List built from the class's ListBuilder
+    # @param current_step_name [String, nil] The name of the current step, if specified.
+    # @return [List::Base] The List built from the class's ListBuilder.
     def onboarding(current_step_name = nil)
-      list_builder.build!(current_step_name)
+      list_builder.build(current_step_name)
     end
   end
 
@@ -50,8 +50,8 @@ module Onboardable
   module InstanceMethods
     # Builds the onboarding list and optionally sets the current step.
     #
-    # @param current_step_name [String, nil] the name of the current step, if specified
-    # @return [List::Base] the List built from the class's ListBuilder
+    # @param current_step_name [String, nil] The name of the current step, if specified.
+    # @return [List::Base] The List built from the class's ListBuilder.
     def onboarding(current_step_name = nil)
       self.class.onboarding(current_step_name)
     end

data/onboardable.gemspec

@@ -0,0 +1,51 @@
+# frozen_string_literal: true
+
+require_relative 'lib/onboardable/version'
+
+Gem::Specification.new do |spec|
+  spec.name = 'onboardable'
+  spec.version = Onboardable::VERSION
+  spec.authors = ['Artem Skrynnyk']
+  spec.email = ['skrynnyk.artem@coaxsoft.com']
+
+  spec.summary = 'Streamlines onboarding process integration'
+  spec.description = 'Provides tools for easy setup of custom onboarding to boost engagement.'
+  spec.homepage = 'https://github.com/dmrAnderson/onboardable'
+  spec.license = 'MIT'
+  spec.required_ruby_version = '>= 3.0.0'
+
+  # spec.metadata["allowed_push_host"] = "TODO: Set to your gem server 'https://example.com'"
+
+  spec.metadata['homepage_uri'] = spec.homepage
+  # spec.metadata['source_code_uri'] = "TODO: Put your gem's public repo URL here."
+  spec.metadata['changelog_uri'] = 'https://github.com/dmrAnderson/onboardable/blob/main/CHANGELOG.md'
+  spec.metadata['bug_tracker_uri'] = 'https://github.com/dmrAnderson/onboardable/issues'
+  spec.metadata['documentation_uri'] = 'https://rubydoc.info/gems/onboardable'
+
+  # Specify which files should be added to the gem when it is released.
+  # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
+  spec.files = Dir.chdir(__dir__) do
+    `git ls-files -z`.split("\x0").reject do |f|
+      (f == __FILE__) || f.match(%r{\A(?:(?:bin|spec)/|\.(?:git|rspec|rubocop))})
+    end
+  end
+
+  spec.bindir = 'exe'
+  spec.executables = spec.files.grep(%r{\Aexe/}) { |f| File.basename(f) }
+  spec.require_paths = ['lib']
+
+  # Uncomment to register a new dependency of your gem
+  # spec.add_dependency "example-gem", "~> 1.0"
+
+  # For more information and examples about making a new gem, check out our
+  # guide at: https://bundler.io/guides/creating_gem.html
+  spec.add_development_dependency 'rake', '~> 13.2', '>= 13.2.1'
+  spec.add_development_dependency 'rspec', '~> 3.13'
+  spec.add_development_dependency 'rubocop', '~> 1.64', '>= 1.64.1'
+  spec.add_development_dependency 'rubocop-performance', '~> 1.21'
+  spec.add_development_dependency 'rubocop-rake', '~> 0.6.0'
+  spec.add_development_dependency 'rubocop-rspec', '~> 2.29', '>= 2.29.2'
+  spec.add_development_dependency 'simplecov', '~> 0.22.0'
+
+  spec.metadata['rubygems_mfa_required'] = 'true'
+end

data/sig/onboardable/list/builder.rbs

@@ -9,10 +9,10 @@ module Onboardable
       def create_step: (String, Hash[Symbol, untyped]) -> Step
       alias step create_step
 
-      def create_step_from!: (Class) -> Step
-      alias step_from create_step_from!
+      def create_step_from: (Class) -> Step
+      alias step_from create_step_from
 
-      def build!: (String?) -> Base
+      def build: (String?) -> Base
 
       private
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: onboardable
 version: !ruby/object:Gem::Version
-  version: 1.2.0
+  version: 1.2.1
 platform: ruby
 authors:
 - Artem Skrynnyk
-autorequire:
+autorequire: 
 bindir: exe
 cert_chain: []
-date: 2024-05-25 00:00:00.000000000 Z
+date: 2024-06-01 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rake
@@ -51,6 +51,9 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: '1.64'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 1.64.1
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
@@ -58,6 +61,9 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: '1.64'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 1.64.1
 - !ruby/object:Gem::Dependency
   name: rubocop-performance
   requirement: !ruby/object:Gem::Requirement
@@ -127,8 +133,6 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- ".rspec"
-- ".rubocop.yml"
 - CHANGELOG.md
 - CODE_OF_CONDUCT.md
 - Gemfile
@@ -144,6 +148,7 @@ files:
 - lib/onboardable/step.rb
 - lib/onboardable/utils/warnings.rb
 - lib/onboardable/version.rb
+- onboardable.gemspec
 - sig/onboardable.rbs
 - sig/onboardable/errors.rbs
 - sig/onboardable/list/base.rbs
@@ -160,7 +165,7 @@ metadata:
   bug_tracker_uri: https://github.com/dmrAnderson/onboardable/issues
   documentation_uri: https://rubydoc.info/gems/onboardable
   rubygems_mfa_required: 'true'
-post_install_message:
+post_install_message: 
 rdoc_options: []
 require_paths:
 - lib
@@ -175,8 +180,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.5.10
-signing_key:
+rubygems_version: 3.5.9
+signing_key: 
 specification_version: 4
 summary: Streamlines onboarding process integration
 test_files: []

data/.rspec

@@ -1,4 +0,0 @@
---format documentation
---color
---require spec_helper
---order rand

data/.rubocop.yml

@@ -1,11 +0,0 @@
-require:
-  - rubocop-performance
-  - rubocop-rspec
-  - rubocop-rake
-
-AllCops:
-  NewCops: enable
-  TargetRubyVersion: 3.0.0
-
-Gemspec/DevelopmentDependencies:
-  EnforcedStyle: gemspec