validation_errors 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 8679caa07860e4574fa21e0ebe978a31405fadb47f5c2ec9bae0b5d2f801e349
+  data.tar.gz: a5d24ff1ee7c2f2a5f0aea3c0068cb60b2c8467f20f99c67ad57f0a292d0f877
+SHA512:
+  metadata.gz: 1e7b20f0989065c49e2f7d42723f962e122e1a899248e1544f0e487bf5e9f4a458b8eea058c94cbeedc5ccacd893a26b8cb041687aed0301fd8e9b40934188d1
+  data.tar.gz: 24d4b7c52ba5a8514a1583f875124c511bcb9107164cc2c061dfecc33cb6b8c9f5edb06c96612ec661ed395efebe4b354788fa32f1c9a606577d7ee61b6e428c

data/.semaphore/main-deploy.yml

@@ -0,0 +1,18 @@
+version: v1.0
+name: main-deploy
+agent:
+  machine:
+    type: e1-standard-2
+    os_image: ubuntu1804
+
+blocks:
+  - name: main-deploy
+    task:
+      secrets:
+        - name: rubygems-deploy
+      jobs:
+        - name: main-deploy
+          commands:
+            - checkout --use-cache
+            - gem build validation_errors
+            - gem push validation_errors-*.gem

data/.semaphore/semaphore.yml

@@ -0,0 +1,32 @@
+version: "v1.0"
+name: validation_errors
+agent:
+  machine:
+    type: e1-standard-2
+    os_image: ubuntu1804
+auto_cancel:
+  running:
+    when: "true"
+
+blocks:
+  - name: tests
+    execution_time_limit:
+      minutes: 10
+    task:
+      secrets:
+        - name: validation_errors
+      prologue:
+        commands:
+          - checkout --use-cache
+          - cache restore
+          - bundle config set path 'vendor/bundle'
+          - bundle install -j 4
+          - cache store
+      jobs:
+        - name: tests
+          commands:
+            - bundle exec standardrb
+            - bundle exec rake
+promotions:
+  - name: main
+    pipeline_file: main-deploy.yml

data/.standard.yml

@@ -0,0 +1,3 @@
+# For available configuration options, see:
+#   https://github.com/testdouble/standard
+ruby_version: 2.6

data/CHANGELOG.md

@@ -0,0 +1,5 @@
+## [Unreleased]
+
+## [0.1.0] - 2022-09-19
+
+- Initial release

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,84 @@
+# 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 coorasse@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.

data/Gemfile

@@ -0,0 +1,6 @@
+# frozen_string_literal: true
+
+source "https://rubygems.org"
+
+# Specify your gem's dependencies in validation_errors.gemspec
+gemspec

data/Gemfile.lock

@@ -0,0 +1,68 @@
+PATH
+  remote: .
+  specs:
+    validation_errors (0.1.0)
+      activerecord (>= 4.1.0)
+      zeitwerk (>= 2.0.0)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    activemodel (7.0.4)
+      activesupport (= 7.0.4)
+    activerecord (7.0.4)
+      activemodel (= 7.0.4)
+      activesupport (= 7.0.4)
+    activesupport (7.0.4)
+      concurrent-ruby (~> 1.0, >= 1.0.2)
+      i18n (>= 1.6, < 2)
+      minitest (>= 5.1)
+      tzinfo (~> 2.0)
+    ast (2.4.2)
+    concurrent-ruby (1.1.10)
+    i18n (1.12.0)
+      concurrent-ruby (~> 1.0)
+    minitest (5.16.3)
+    parallel (1.22.1)
+    parser (3.1.2.1)
+      ast (~> 2.4.1)
+    rainbow (3.1.1)
+    rake (13.0.6)
+    regexp_parser (2.5.0)
+    rexml (3.2.5)
+    rubocop (1.10.0)
+      parallel (~> 1.10)
+      parser (>= 3.0.0.0)
+      rainbow (>= 2.2.2, < 4.0)
+      regexp_parser (>= 1.8, < 3.0)
+      rexml
+      rubocop-ast (>= 1.2.0, < 2.0)
+      ruby-progressbar (~> 1.7)
+      unicode-display_width (>= 1.4.0, < 3.0)
+    rubocop-ast (1.21.0)
+      parser (>= 3.1.1.0)
+    rubocop-performance (1.9.2)
+      rubocop (>= 0.90.0, < 2.0)
+      rubocop-ast (>= 0.4.0)
+    ruby-progressbar (1.11.0)
+    sqlite3 (1.5.0-arm64-darwin)
+    standard (0.13.0)
+      rubocop (= 1.10.0)
+      rubocop-performance (= 1.9.2)
+    tzinfo (2.0.5)
+      concurrent-ruby (~> 1.0)
+    unicode-display_width (2.3.0)
+    zeitwerk (2.6.0)
+
+PLATFORMS
+  arm64-darwin-21
+
+DEPENDENCIES
+  minitest (~> 5.0)
+  rake (~> 13.0)
+  sqlite3 (~> 1.5.0)
+  standard (~> 0.13.0)
+  validation_errors!
+
+BUNDLED WITH
+   2.3.21

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2022 Alessandro Rodi
+
+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.

data/README.md

@@ -0,0 +1,205 @@
+# ValidationErrors 😱
+
+_Because shit happens_
+
+This gem helps you keep track of the ActiveRecord validation errors that have been triggered on a model.
+
+It persists them on a `validation_errors` database table the following information:
+* time of the error
+* model name
+* model id (if available)
+* action (create/update)
+* errors.details (hash)
+
+## Why?
+
+Validation errors happen. In some applications it might be interesting to keep track of them.
+This gem has been extracted from various Ruby On Rails apps where I had this need.
+
+If you have a validation error, you want to keep track of it...but how?
+* You can use a logger, but then you have to parse the logs to get the information you need. i.e. is not structured.
+* You can use an error tracker, like Sentry, but this isn't really an error, is it? If you have many, it might pollute your errors tracker.
+* You can use a database table, and that's what this gem does.
+
+This gem will keep track of the errors, and give you all the freedom to query it and extract statistics and make analysis.
+By analysing from time to time these data, you might found out the following:
+* Your UI sucks
+* Your validations are too strict
+* Your validations are too loose
+* Your client-side validations are not working
+* Your client-side validations are too loose
+* This bullet point list has been generated by copilot
+
+## Installation
+
+Install the gem and add it to the application's Gemfile by executing:
+
+    $ bundle add validation_errors
+
+If bundler is not being used to manage dependencies, install the gem by executing:
+
+    $ gem install validation_errors
+
+## Usage
+
+Run `bin/rails g validation_errors:install` to create the migration.
+Stop evil spring, if the generator is not found: `spring stop`.
+
+Run `bin/rails db:migrate` to create the tables.
+
+The migration will create a `validation_errors` table. Check the migration for details.
+If you use [Scenic](https://github.com/scenic-views/scenic) it will also generate some useful views.
+
+### Manual
+
+You can now manually track errors by calling `ValidationErrors.track`:
+
+```ruby
+ValidationErrors.track(your_invalid_model)
+```
+
+An example could be the following:
+
+```ruby
+def create
+    @user = User.new(user_params)
+    if @user.save
+        redirect_to @user
+    else
+        ValidationError.track(@user)
+        render :new
+    end
+end
+```
+
+Yes, this will execute an additinoal INSERT into your database. Keep it in mind.
+
+### Automatic
+
+You can also track validation errors automatically by adding `track_validation_errors` in your model.
+
+```ruby
+class User < ApplicationRecord
+    track_validation_errors
+end
+```
+
+by doing so, validation errors are tracked automatically on each `save`, `save!`, `update`, or `update!` call on your model.
+
+### Global
+
+You can of course enable it on all you models by specifying it in ApplicationRecord directly:
+
+```ruby
+class ApplicationRecord < ActiveRecord::Base
+    self.abstract_class = true
+    track_validation_errors
+end
+```
+
+We currently don't support (PR welcome):
+* enable globally and disable on a specific model `skip_track_validation_errors`
+* enable only for specific actions `track_validation_errors only: [:create]`
+* disable only for specific actions `track_validation_errors except: [:create]`
+* enable only for bang or non-bang methods `track_validation_errors only_bang: true`,  `track_validation_errors only_non_bang: true`
+
+
+## Query your data
+
+Now that you have installed the gem and started tracking, let's take a look at how the data are persisted and how you can query them.
+We store the errors in exactly the same format returned by ActiveRecord `errors.details`.
+
+Given a book, that failed to save because of validation errors, you'll get the following:
+
+| id | invalid_model_name | invalid_model_id | action | details                                                                                               |
+|----|--------------------|------------------|--------|-------------------------------------------------------------------------------------------------------|
+| 1  | Book               | 1                | create | `{ "base" => [{ "error" => "invalid" }], "title" => [{ "error" => "blank" }, {"error" => "invalid"}] }` |
+
+The following SQL (Postgres only!) can be used to obtain a flattened view. 
+You can use it in your queries, or create a database view:
+
+```sql
+select validation_errors.invalid_model_name,
+       validation_errors.invalid_model_id,
+       validation_errors.action,
+       validation_errors.created_at,
+       json_data.key as error_column,
+       json_array_elements(json_data.value)->>'error' as error_type
+from validation_errors, json_each(validation_errors.details) as json_data
+```
+
+**The gem will already create this view for you, if you use [Scenic](https://github.com/scenic-views/scenic).**
+
+The result is the following:
+
+| invalid_model_name | invalid_model_id | action | error_column | error_type |
+|--------------------|------------------|--------|--------------|------------|
+| Book               | 1                | create | base         |  invalid   |
+| Book               | 1                | create | title        |  blank     |
+| Book               | 1                | create | title        |  invalid   |
+
+
+Let's now check some useful queries:
+
+### Count the number of errors per day
+
+```sql
+select count(*), date(created_at) 
+from validation_errors 
+group by date(created_at) 
+order by date(created_at) desc;
+```
+
+Please use [groupdate](https://github.com/ankane/groupdate) for more reliable results when grouping by date.
+
+```ruby
+ValidationError.group_by_day(:created_at).count
+```
+
+### Count the number of errors per model and attribute
+
+```sql
+select validation_errors.invalid_model_name, 
+       json_data.key as error_column, 
+       json_array_elements(json_data.value)->>'error' as error_type, 
+       count(*)
+from validation_errors, 
+     json_each(validation_errors.details) as json_data
+group by 1, 2, 3
+order by 4 desc
+```
+
+or, if you have the view above:
+
+```sql
+select invalid_model_name, error_column, count(*)
+from validation_errors_flat
+group by 1, 2
+```
+
+```ruby
+FlatValidationError.group(:invalid_model_name, :error_column).count
+```
+
+## 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/coorasse/validation_errors. 
+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/coorasse/validation_errors/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 ValidationErrors project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/coorasse/validation_errors/blob/master/CODE_OF_CONDUCT.md).

data/Rakefile

@@ -0,0 +1,14 @@
+# frozen_string_literal: true
+
+require "bundler/gem_tasks"
+require "rake/testtask"
+
+Rake::TestTask.new(:test) do |t|
+  t.libs << "test"
+  t.libs << "lib"
+  t.test_files = FileList["test/**/test_*.rb"]
+end
+
+require "standard/rake"
+
+task default: %i[test standard]

data/lib/flat_validation_error.rb

@@ -0,0 +1,7 @@
+# frozen_string_literal: true
+
+class FlatValidationError < ActiveRecord::Base
+  def readonly?
+    true
+  end
+end

data/lib/generators/templates/create_flat_validation_errors.rb.tt

@@ -0,0 +1,5 @@
+class CreateFlatValidationErrors < ActiveRecord::Migration[<%= ActiveRecord::Migration.current_version %>]
+  def change
+    create_view :flat_validation_errors
+  end
+end

data/lib/generators/templates/create_validation_errors_table.rb.tt

@@ -0,0 +1,11 @@
+class CreateValidationErrorsTable < ActiveRecord::Migration[<%= ActiveRecord::Migration.current_version %>]
+  def change
+    create_table :validation_errors do |t|
+      t.string :invalid_model_name, index: true
+      t.bigint :invalid_model_id
+      t.string :action, index: true
+      t.json :details
+      t.timestamps null: false
+    end
+  end
+end

data/lib/generators/templates/flat_validation_errors_v01.sql.tt

@@ -0,0 +1,7 @@
+select validation_errors.invalid_model_name,
+       validation_errors.invalid_model_id,
+       validation_errors.action,
+       validation_errors.created_at,
+       json_data.key as error_column,
+       json_array_elements(json_data.value)->>'error' as error_type
+from validation_errors, json_each(validation_errors.details) as json_data

data/lib/generators/validation_errors/install_generator.rb

@@ -0,0 +1,31 @@
+# frozen_string_literal: true
+
+require "rails/generators/base"
+require "rails/generators/migration"
+
+module ValidationErrors
+  module Generators
+    class InstallGenerator < Rails::Generators::Base
+      include Rails::Generators::Migration
+
+      source_root File.expand_path("../../templates", __FILE__)
+
+      # Implement the required interface for Rails::Generators::Migration.
+      def self.next_migration_number(dirname)
+        next_migration_number = current_migration_number(dirname) + 1
+        ActiveRecord::Migration.next_migration_number(next_migration_number)
+      end
+
+      desc "Copy migrations to your application."
+      def copy_migrations
+        migration_template "create_validation_errors_table.rb", "db/migrate/create_validation_errors_table.rb"
+        if defined?(Scenic)
+          migration_template "create_flat_validation_errors.rb", "db/migrate/create_flat_validation_errors.rb"
+          copy_file "flat_validation_errors_v01.sql", "db/views/flat_validation_errors_v01.sql"
+        else
+          puts "Scenic is not installed so we will skip the creation of the flat_validation_errors view.\nCheck the README for more information."
+        end
+      end
+    end
+  end
+end

data/lib/validation_error.rb

@@ -0,0 +1,10 @@
+# frozen_string_literal: true
+
+class ValidationError < ActiveRecord::Base
+  def self.track(invalid_model)
+    create!(invalid_model_name: invalid_model.class.name,
+            invalid_model_id: invalid_model.id,
+            details: invalid_model.errors.details,
+            action: invalid_model.persisted? ? "update" : "create")
+  end
+end

data/lib/validation_errors.rb

@@ -0,0 +1,43 @@
+# frozen_string_literal: true
+
+require "active_record"
+require "zeitwerk"
+
+loader = Zeitwerk::Loader.for_gem(warn_on_extra_files: false)
+loader.collapse("#{__dir__}/validation_errors")
+loader.ignore("#{__dir__}/generators")
+loader.setup
+
+module ValidationErrors
+  module Trackable
+    def self.included(base)
+      base.extend ClassMethods
+    end
+
+    # :nodoc:
+    module ClassMethods
+      def track_validation_errors
+        include InstanceMethods
+      end
+    end
+
+    module InstanceMethods
+      def save(**options)
+        super.tap do |result|
+          ValidationError.track(self) unless result
+        end
+      end
+
+      # Attempts to save the record just like {ActiveRecord::Base#save}[rdoc-ref:Base#save] but
+      # will raise an ActiveRecord::RecordInvalid exception instead of returning +false+ if the record is not valid.
+      def save!(**options)
+        super
+      rescue ActiveRecord::RecordInvalid
+        ValidationError.track(self)
+        raise
+      end
+    end
+  end
+end
+
+ActiveRecord::Base.include ValidationErrors::Trackable

data/sig/lib/validation_errors.rbs

@@ -0,0 +1,20 @@
+class ValidationErrors < ActiveRecord::Base
+  def self.track: (untyped invalid_model) -> untyped
+
+  module Trackable
+    def self.included: (untyped base) -> untyped
+
+    # :nodoc:
+    module ClassMethods
+      def track_validation_errors: () -> untyped
+    end
+
+    module InstanceMethods
+      def save: (**untyped options) -> untyped
+
+      # Attempts to save the record just like {ActiveRecord::Base#save}[rdoc-ref:Base#save] but
+      # will raise an ActiveRecord::RecordInvalid exception instead of returning +false+ if the record is not valid.
+      def save!: (**untyped options) -> untyped
+    end
+  end
+end

data/sig/validation_errors.rbs

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

metadata

@@ -0,0 +1,151 @@
+--- !ruby/object:Gem::Specification
+name: validation_errors
+version: !ruby/object:Gem::Version
+  version: 0.1.0
+platform: ruby
+authors:
+- Alessandro Rodi
+autorequire:
+bindir: exe
+cert_chain: []
+date: 2022-12-08 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: activerecord
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 4.1.0
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 4.1.0
+- !ruby/object:Gem::Dependency
+  name: zeitwerk
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 2.0.0
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 2.0.0
+- !ruby/object:Gem::Dependency
+  name: sqlite3
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 1.5.0
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 1.5.0
+- !ruby/object:Gem::Dependency
+  name: standard
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 0.13.0
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 0.13.0
+- !ruby/object:Gem::Dependency
+  name: rake
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '13.0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '13.0'
+- !ruby/object:Gem::Dependency
+  name: minitest
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '5.0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '5.0'
+description: Easily track all the validation errors on your database so that you can
+  analyse them.
+email:
+- rodi@hey.com
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- ".semaphore/main-deploy.yml"
+- ".semaphore/semaphore.yml"
+- ".standard.yml"
+- CHANGELOG.md
+- CODE_OF_CONDUCT.md
+- Gemfile
+- Gemfile.lock
+- LICENSE.txt
+- README.md
+- Rakefile
+- lib/flat_validation_error.rb
+- lib/generators/templates/create_flat_validation_errors.rb.tt
+- lib/generators/templates/create_validation_errors_table.rb.tt
+- lib/generators/templates/flat_validation_errors_v01.sql.tt
+- lib/generators/validation_errors/install_generator.rb
+- lib/validation_error.rb
+- lib/validation_errors.rb
+- sig/lib/validation_errors.rbs
+- sig/validation_errors.rbs
+homepage: https://github.com/coorasse/validation_errors
+licenses:
+- MIT
+metadata:
+  homepage_uri: https://github.com/coorasse/validation_errors
+  source_code_uri: https://github.com/coorasse/validation_errors
+  changelog_uri: https://github.com/coorasse/validation_errors/blob/main/CHANGELOG.md
+  funding_uri: https://github.com/sponsors/coorasse
+post_install_message:
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: 2.6.0
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubygems_version: 3.3.10
+signing_key:
+specification_version: 4
+summary: Track ActiveRecord validation errors on database
+test_files: []