hospital 0.2.0 → 0.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 6f8da0744448857dbd214916e8a2767f17c1ffa2fac62ebee528c9b6fdd045ea
-  data.tar.gz: ac90c8b38035d8dee4f968161148042e41b774ad574b311a63ee480b82d896e1
+  metadata.gz: b1df079afc135900573cf9a989a01d9dbc1ef917ead9e5f6898ea3faa94c0523
+  data.tar.gz: 0e82ab36be7b2dd80f6ec6212d62074d48746ad54710e6aff78da0e630878fe1
 SHA512:
-  metadata.gz: 870e3c40165b74923f4da76e54a58ec5ee2d32b7803d57eb59ce492d41b4686ec531f14af7726a264badb19db086c118e3fd80db9d7308201500b3e6d93a433f
-  data.tar.gz: e0dd681f5d4bfdcab6ce3dcd4e741140b02182f93a6746990b12c2ad141085ae0974823672de4999090313876c5f9ed785e08353510336343dc0ae160e880302
+  metadata.gz: 4b0a6363c4f08c17514ef1557e7aefe59abb9b04beb2b961c43db1ea9faef80265cbb32e66c5f15fb887632402dfd698b7d74f197a33531122b1b5ab0d229538
+  data.tar.gz: d441ee4bd337d0820373a19f0f079624d3fc9f62a56d69b6f3211039424bd66187934a885bf1650c3038aef0a4b328fe967300082ff3bd6f49f04a816e221661

data/lib/hospital/diagnosis.rb

@@ -0,0 +1,86 @@
+class Hospital::Diagnosis  
+  attr_reader :infos, :warnings, :errors, :name, :results
+
+  def initialize name
+    @name               = name.to_s
+    reset
+  end
+
+  def reset
+    @infos    = []
+    @warnings = []
+    @errors   = []
+    @results  = []
+  end
+
+  def require_env_vars env_vars=[]
+    if (missing_vars = env_vars.select{|var| ENV[var].nil? || ENV[var].empty? }).any?
+      add_error("These necessary ENV vars are not set: #{variable_list(missing_vars)}.")
+    else
+      add_info("All necessary ENV vars are set.")
+    end
+  end
+
+  def variable_list vars
+    "[#{vars.map{|v| "'#{v}'"}.join(', ')}]"
+  end
+
+  class Result
+    attr_reader :message, :prefix
+
+    def initialize message
+      @message = message
+    end
+
+    def output
+      "#{prefix} #{message.gsub(/\n\z/, '').gsub(/\n/, prefix ? "\n   " : "\n")}"
+    end
+
+    def put 
+      puts output
+    end
+  end
+
+  class Info < Result
+    def prefix; '🟢' end
+  end
+
+  class Warning < Result
+    def prefix; '🟠'; end
+  end
+
+  class Error < Result
+    def prefix; '🔴'; end
+  end
+
+  def add_info message
+    info = Info.new message
+    @infos    << info
+    @results  << info
+  end
+
+  def add_warning message
+    warning = Warning.new message
+    @warnings << warning
+    @results  << warning
+  end
+
+  def add_error message
+    error = Error.new message
+    @errors   << error
+    @results  << error
+  end
+
+  def put_results
+    put_header "Checking #{name}:"
+    results.each &:put
+  end
+
+  private
+
+  def put_header message
+    puts ''
+    puts "### #{message}"
+  end
+
+end

data/lib/hospital/tasks/checkup.rake

@@ -0,0 +1,10 @@
+# encoding: utf-8
+
+require_relative '../../hospital'
+
+desc 'Check system setup sanity.'
+task :doctor => [] do
+  # at_exit { Rake::Task['doctor:summary'].invoke if $!.nil? }
+
+  Hospital.checkup_all
+end

data/lib/hospital/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Hospital
-  VERSION = "0.2.0"
+  VERSION = "0.3.0"
 end

data/lib/hospital.rb

@@ -1,8 +1,49 @@
 # frozen_string_literal: true
 
 require_relative "hospital/version"
+require_relative "hospital/diagnosis"
 
 module Hospital
+  require_relative 'railtie' if defined?(Rails)
+
   class Error < StandardError; end
-  # Your code goes here...
+
+  @@checkups    = {}
+  @@diagnosises = {}
+
+  def self.included(base)
+    raise Hospital::Error.new("Cannot include Hospital, please extend instead.")
+  end
+
+  def self.extended(base)
+    @@checkups[base] = ->(diagnosis) do
+      diagnosis.add_warning("#{base}: No checks defined! Please call checkup with a lambda.")
+    end
+    @@diagnosises[base] = Hospital::Diagnosis.new(base)
+  end
+
+  def checkup code
+    @@checkups[self] = code
+  end
+
+  def self.checkup klass
+    @@diagnosises[klass].reset
+    @@checkups[klass].call(@@diagnosises[klass])
+    @@diagnosises[klass]
+  end
+
+  def self.checkup_all
+    errcount = 0
+    @@checkups.keys.each do |klass|
+      checkup(klass)
+      diagnosis = @@diagnosises[klass]
+      diagnosis.put_results
+      errcount += diagnosis.errors.count
+    end
+
+    puts <<~END
+      Summary:"
+      Errors: #{errcount}
+    END
+  end
 end

data/lib/railtie.rb

@@ -0,0 +1,14 @@
+# lib/railtie.rb
+require 'hospital'
+require 'rails'
+
+module Hospital
+  class Railtie < Rails::Railtie
+    railtie_name :hospital
+
+    rake_tasks do
+      path = File.expand_path(__dir__)
+      Dir.glob("#{path}/hospital/tasks/*.rake").each { |f| load f }
+    end
+  end
+end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: hospital
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 0.3.0
 platform: ruby
 authors:
 - Alexander
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2023-04-05 00:00:00.000000000 Z
+date: 2023-12-19 00:00:00.000000000 Z
 dependencies: []
 description: Imagine a team of little doctors creating diagnoses and creating a useful
   report.
@@ -18,17 +18,13 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- ".rspec"
-- CHANGELOG.md
-- CODE_OF_CONDUCT.md
-- Gemfile
 - LICENSE.txt
 - README.md
-- Rakefile
-- hospital.gemspec
 - lib/hospital.rb
+- lib/hospital/diagnosis.rb
+- lib/hospital/tasks/checkup.rake
 - lib/hospital/version.rb
-- sig/hospital.rbs
+- lib/railtie.rb
 homepage: https://github.com/giantmonkey/hospital
 licenses:
 - MIT
@@ -44,14 +40,14 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: 2.6.0
+      version: 2.7.8
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.2.33
+rubygems_version: 3.2.32
 signing_key:
 specification_version: 4
 summary: A framwork for app self-checks

data/.rspec

@@ -1,3 +0,0 @@
---format documentation
---color
---require spec_helper

data/CHANGELOG.md

@@ -1,5 +0,0 @@
-## [Unreleased]
-
-## [0.1.0] - 2023-04-05
-
-- Initial release

data/CODE_OF_CONDUCT.md

@@ -1,84 +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 alexander@presber.net. 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/Gemfile

@@ -1,10 +0,0 @@
-# frozen_string_literal: true
-
-source "https://rubygems.org"
-
-# Specify your gem's dependencies in hospital.gemspec
-gemspec
-
-gem "rake", "~> 13.0"
-
-gem "rspec", "~> 3.0"

data/Rakefile

@@ -1,8 +0,0 @@
-# frozen_string_literal: true
-
-require "bundler/gem_tasks"
-require "rspec/core/rake_task"
-
-RSpec::Core::RakeTask.new(:spec)
-
-task default: :spec

data/hospital.gemspec

@@ -1,39 +0,0 @@
-# frozen_string_literal: true
-
-require_relative "lib/hospital/version"
-
-Gem::Specification.new do |spec|
-  spec.name     = "hospital"
-  spec.version  = Hospital::VERSION
-  spec.authors  = ["Alexander"]
-  spec.email    = ["alexander@presber.net"]
-
-  spec.summary                = "A framwork for app self-checks"
-  spec.description            = "Imagine a team of little doctors creating diagnoses and creating a useful report."
-  spec.homepage               = "https://github.com/giantmonkey/hospital"
-  spec.license                = "MIT"
-  spec.required_ruby_version  = ">= 2.6.0"
-
-  # spec.metadata["allowed_push_host"]  = "'https://rubygems.org'"
-
-  spec.metadata["homepage_uri"]       = spec.homepage
-  spec.metadata["source_code_uri"]    = "https://github.com/giantmonkey/hospital"
-  spec.metadata["changelog_uri"]      = "https://github.com/giantmonkey/hospital/blob/main/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|
-      (f == __FILE__) || f.match(%r{\A(?:(?:bin|test|spec|features)/|\.(?:git|circleci)|appveyor)})
-    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

data/sig/hospital.rbs

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