pax_global_header00006660000000000000000000000064145721633720014524gustar00rootroot0000000000000052 comment=71959b8d5952cd9f11361c08cd7b1bf91baaad4c solid-process-0.0.0/000077500000000000000000000000001457216337200143075ustar00rootroot00000000000000solid-process-0.0.0/.github/000077500000000000000000000000001457216337200156475ustar00rootroot00000000000000solid-process-0.0.0/.github/workflows/000077500000000000000000000000001457216337200177045ustar00rootroot00000000000000solid-process-0.0.0/.github/workflows/main.yml000066400000000000000000000007021457216337200213520ustar00rootroot00000000000000name: Ruby on: push: branches: - master pull_request: jobs: build: runs-on: ubuntu-latest name: Ruby ${{ matrix.ruby }} strategy: matrix: ruby: - '3.2.2' steps: - uses: actions/checkout@v4 - name: Set up Ruby uses: ruby/setup-ruby@v1 with: ruby-version: ${{ matrix.ruby }} bundler-cache: true - name: Run the default task run: bundle exec rake solid-process-0.0.0/.gitignore000066400000000000000000000001271457216337200162770ustar00rootroot00000000000000/.bundle/ /.yardoc /_yardoc/ /coverage/ /doc/ /pkg/ /spec/reports/ /tmp/ Gemfile.lock solid-process-0.0.0/.rubocop.yml000066400000000000000000000003341457216337200165610ustar00rootroot00000000000000AllCops: TargetRubyVersion: 2.6 Style/StringLiterals: Enabled: true EnforcedStyle: double_quotes Style/StringLiteralsInInterpolation: Enabled: true EnforcedStyle: double_quotes Layout/LineLength: Max: 120 solid-process-0.0.0/CHANGELOG.md000066400000000000000000000000741457216337200161210ustar00rootroot00000000000000## [Unreleased] ## [0.1.0] - 2024-03-06 - Initial release solid-process-0.0.0/CODE_OF_CONDUCT.md000066400000000000000000000121511457216337200171060ustar00rootroot00000000000000# 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 rodrigo.serradura@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. solid-process-0.0.0/Gemfile000066400000000000000000000003151457216337200156010ustar00rootroot00000000000000# frozen_string_literal: true source "https://rubygems.org" # Specify your gem's dependencies in solid-process.gemspec gemspec gem "rake", "~> 13.0" gem "minitest", "~> 5.16" gem "rubocop", "~> 1.21" solid-process-0.0.0/LICENSE.txt000066400000000000000000000020741457216337200161350ustar00rootroot00000000000000The MIT License (MIT) Copyright (c) 2024 Rodrigo Serradura 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. solid-process-0.0.0/README.md000066400000000000000000000044161457216337200155730ustar00rootroot00000000000000# Solid::Process TODO: Delete this and the text below, and describe your gem Welcome to your new gem! In this directory, you'll find the files you need to be able to package up your Ruby library into a gem. Put your Ruby code in the file `lib/solid/process`. To experiment with that code, run `bin/console` for an interactive prompt. ## Installation TODO: Replace `UPDATE_WITH_YOUR_GEM_NAME_IMMEDIATELY_AFTER_RELEASE_TO_RUBYGEMS_ORG` with your gem name right after releasing it to RubyGems.org. Please do not do it earlier due to security reasons. Alternatively, replace this section with instructions to install your gem from git if you don't plan to release to RubyGems.org. Install the gem and add to the application's Gemfile by executing: $ bundle add UPDATE_WITH_YOUR_GEM_NAME_IMMEDIATELY_AFTER_RELEASE_TO_RUBYGEMS_ORG If bundler is not being used to manage dependencies, install the gem by executing: $ gem install UPDATE_WITH_YOUR_GEM_NAME_IMMEDIATELY_AFTER_RELEASE_TO_RUBYGEMS_ORG ## Usage TODO: Write usage instructions here ## Development After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake test` to run the tests. 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`. To release a new version, update the version number in `version.rb`, and then run `bundle exec 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](https://rubygems.org). ## Contributing Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/solid-process. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://github.com/[USERNAME]/solid-process/blob/master/CODE_OF_CONDUCT.md). ## License The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT). ## Code of Conduct Everyone interacting in the Solid::Process project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/[USERNAME]/solid-process/blob/master/CODE_OF_CONDUCT.md). solid-process-0.0.0/Rakefile000066400000000000000000000003071457216337200157540ustar00rootroot00000000000000# frozen_string_literal: true require "bundler/gem_tasks" require "minitest/test_task" Minitest::TestTask.create require "rubocop/rake_task" RuboCop::RakeTask.new task default: %i[test rubocop] solid-process-0.0.0/bin/000077500000000000000000000000001457216337200150575ustar00rootroot00000000000000solid-process-0.0.0/bin/console000077500000000000000000000004371457216337200164530ustar00rootroot00000000000000#!/usr/bin/env ruby # frozen_string_literal: true require "bundler/setup" require "solid/process" # You can add fixtures and/or initialization code here to make experimenting # with your gem easier. You can also use a different console, if you like. require "irb" IRB.start(__FILE__) solid-process-0.0.0/bin/setup000077500000000000000000000002031457216337200161400ustar00rootroot00000000000000#!/usr/bin/env bash set -euo pipefail IFS=$'\n\t' set -vx bundle install # Do any other automated setup that you need to do here solid-process-0.0.0/lib/000077500000000000000000000000001457216337200150555ustar00rootroot00000000000000solid-process-0.0.0/lib/solid/000077500000000000000000000000001457216337200161675ustar00rootroot00000000000000solid-process-0.0.0/lib/solid/process.rb000066400000000000000000000002551457216337200201740ustar00rootroot00000000000000# frozen_string_literal: true require_relative "process/version" module Solid module Process class Error < StandardError; end # Your code goes here... end end solid-process-0.0.0/lib/solid/process/000077500000000000000000000000001457216337200176455ustar00rootroot00000000000000solid-process-0.0.0/lib/solid/process/version.rb000066400000000000000000000001351457216337200216560ustar00rootroot00000000000000# frozen_string_literal: true module Solid module Process VERSION = "0.0.0" end end solid-process-0.0.0/sig/000077500000000000000000000000001457216337200150715ustar00rootroot00000000000000solid-process-0.0.0/sig/solid/000077500000000000000000000000001457216337200162035ustar00rootroot00000000000000solid-process-0.0.0/sig/solid/process.rbs000066400000000000000000000002031457216337200203640ustar00rootroot00000000000000module Solid module Process VERSION: String # See the writing guide of rbs: https://github.com/ruby/rbs#guides end end solid-process-0.0.0/solid-process.gemspec000066400000000000000000000030161457216337200204420ustar00rootroot00000000000000# frozen_string_literal: true require_relative "lib/solid/process/version" Gem::Specification.new do |spec| spec.name = "solid-process" spec.version = Solid::Process::VERSION spec.authors = ["Rodrigo Serradura"] spec.email = ["rodrigo.serradura@gmail.com"] spec.summary = "Ruby on Rails/Business Processes" spec.description = "Ruby on Rails/Business Processes" spec.homepage = "https://github.com/serradura/solid-process" spec.license = "MIT" spec.required_ruby_version = ">= 2.7.0" spec.metadata["allowed_push_host"] = "https://rubygems.org" spec.metadata["homepage_uri"] = spec.homepage spec.metadata["source_code_uri"] = "https://github.com/serradura/solid-process" spec.metadata["changelog_uri"] = "https://github.com/serradura/solid-process/CHANGELOG.md" # 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| (File.expand_path(f) == __FILE__) || f.start_with?(*%w[bin/ test/ spec/ features/ .git .github appveyor Gemfile]) 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 end solid-process-0.0.0/test/000077500000000000000000000000001457216337200152665ustar00rootroot00000000000000solid-process-0.0.0/test/solid/000077500000000000000000000000001457216337200164005ustar00rootroot00000000000000solid-process-0.0.0/test/solid/test_process.rb000066400000000000000000000003671457216337200214500ustar00rootroot00000000000000# frozen_string_literal: true require "test_helper" class Solid::TestProcess < Minitest::Test def test_that_it_has_a_version_number refute_nil ::Solid::Process::VERSION end def test_it_does_something_useful assert false end end solid-process-0.0.0/test/test_helper.rb000066400000000000000000000002121457216337200201240ustar00rootroot00000000000000# frozen_string_literal: true $LOAD_PATH.unshift File.expand_path("../lib", __dir__) require "solid/process" require "minitest/autorun"