rails_or VS dry-validation

Compare rails_or vs dry-validation and see what are their differences.


Cleaner syntax for writing OR Query in Rails 5, 6. And also add #or support to Rails 3 and 4. (by khiav223577)
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
rails_or dry-validation
0 4
94 1,313
- 0.2%
3.6 6.0
8 months ago 7 months ago
Ruby Ruby
MIT License MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.


Posts with mentions or reviews of rails_or. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning rails_or yet.
Tracking mentions began in Dec 2020.


Posts with mentions or reviews of dry-validation. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-09-02.
  • Leveraging complexity of service objects with dry libraries
    3 projects | dev.to | 2 Sep 2021
    ➡️ First, we need to upgrade the validation process. For this will be used the gem dry-validation. It adds validations that are expressed through contract objects.
    3 projects | dev.to | 2 Sep 2021
    ➡️ The most interesting part is the ConductResearchContract. It validates each element of the experiments array for compliance with the schema defined in the ConductExperimentContract. Sadly, now, to run rules for each experiment, you must run them manually like in the rule(:experiments).
  • How to express this data type in Ruby?
    2 projects | /r/ruby | 13 Feb 2021
    I wouldn't add any type validations in my first version. Should they be needed I would use https://github.com/dry-rb/dry-validation.

What are some alternatives?

When comparing rails_or and dry-validation you can also consider the following projects:

Ruby JSON Schema Validator - Ruby JSON Schema Validator

rbs - Type Signature for Ruby


ranked-model - An acts_as_sortable/acts_as_list replacement built for Rails 4+

Enumerize - Enumerated attributes with I18n and ActiveRecord/Mongoid support

Apartment - Database multi-tenancy for Rack (and Rails) applications

ActsAsList - An ActiveRecord plugin for managing lists.

Ancestry - Organise ActiveRecord model into a tree structure

Goldiloader - Just the right amount of Rails eager loading

ActiveRecord Import - A library for bulk insertion of data into your database using ActiveRecord.

activerecord_json_validator - 🔩 ActiveRecord::JSONValidator makes it easy to validate JSON attributes against a JSON schema.