procore-sift 1.0.0 → 1.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 1594b92ce7a641195d2c67b981f3f138648566196d8e56d80d0089689dd7a7b3
-  data.tar.gz: 97efc53749c62bdaad7b5888c5108c52ccf0c091af730a7ab12a9c7bee3d5f3a
+  metadata.gz: 596ec26cb7543f8577252a68435106152cbff901d51a327c8dfa633644c1d69d
+  data.tar.gz: 4bd86a6fd6c758227c22716aa50fd1a46e0cb816213a7ecac20c1f64b6de6f81
 SHA512:
-  metadata.gz: 302c1147b6c5402449a4999492f176aceedf6648180673b5710fb21b522501e8de58945868dd487e286e0de7a403e8c6669431cbcf9565fa42c0b54041da5ffd
-  data.tar.gz: 0d050ee3c4fbeb0a270cb5994efcdd71f926901f3c2db1b79b38d241a17ebe14428b386de10f8b128885c331b334d20b5fedd4b3d153d047bf7a6f17bd9774bf
+  metadata.gz: 24b0c037aaf2f0d1633a70ecbc9e719f2546d368d797dbcb19baeac89d9ecd936e0b1c72cb3089b2707b0998dd23ce36bd70b9a53fe01ebce812208ff79b59a8
+  data.tar.gz: c91c06e910abc752bd41e2345a5e528418a80405692d9db6e7a81006886331e4b984f89dbd212809c8171ee8dbc927159da8b9a532559cd06b177a80b6e753fe

data/README.md

@@ -1,297 +1,45 @@
 # Sift
 
-[![Build Status](https://travis-ci.org/procore/sift.svg?branch=master)](https://travis-ci.org/procore/sift)
+[![Tests](https://github.com/procore/sift/actions/workflows/test.yml/badge.svg)](https://github.com/procore/sift/actions/workflows/test.yml)
 
-A tool to build your own filters and sorts with Rails and Active Record!
+A declarative DSL for building filters and sorts with Rails and Active Record.
 
-## Developer Usage
+## Usage
 
-Include Sift in your controllers, and define some filters.
+Include Sift in your controllers and define filters and sorts:
 
 ```ruby
 class PostsController < ApplicationController
   include Sift
 
   filter_on :title, type: :string
+  filter_on :priority, type: :int
+  filter_on :published_at, type: :datetime
+  filter_on :with_body, type: :scope
 
-  def index
-    render json: filtrate(Post.all)
-  end
-end
-```
-
-This will allow users to pass `?filters[title]=foo` and get the `Post`s with the title `foo`.
-
-Sift will also handle rendering errors using the standard rails errors structure. You can add this to your controller by adding,
-
-```ruby
-before_action :render_filter_errors, unless: :filters_valid?
-
-def render_filter_errors
-  render json: { errors: filter_errors }, status: :bad_request && return
-end
-```
-
-to your controller.
-
-These errors are based on the type that you told sift your param was.
-
-### Filter Types
-
-Every filter must have a type, so that Sift knows what to do with it. The current valid filter types are:
-
-- int - Filter on an integer column
-- decimal - Filter on a decimal column
-- boolean - Filter on a boolean column
-- string - Filter on a string column
-- text - Filter on a text column
-- date - Filter on a date column
-- time - Filter on a time column
-- datetime - Filter on a datetime column
-- scope - Filter on an ActiveRecord scope
-- jsonb - Filter on a jsonb column (supported only in PostgreSQL)
-
-### Filter on Scopes
-
-Just as your filter values are used to scope queries on a column, values you
-pass to a scope filter will be used as arguments to that scope. For example:
+  sort_on :title, type: :string
+  sort_on :priority, type: :int
 
-```ruby
-class Post < ActiveRecord::Base
-  scope :with_body, ->(text) { where(body: text) }
-end
-
-class PostsController < ApplicationController
-  include Sift
-
-  filter_on :with_body, type: :scope
+  before_action :render_filter_errors, unless: :filters_valid?
 
   def index
     render json: filtrate(Post.all)
   end
-end
-```
-
-Passing `?filters[with_body]=my_text` will call the `with_body` scope with
-`my_text` as the argument.
-
-Scopes that accept no arguments are currently not supported.
-
-#### Accessing Params with Filter Scopes
-
-Filters with `type: :scope` have access to the params hash by passing in the desired keys to the `scope_params`. The keys passed in will be returned as a hash with their associated values.
-
-```ruby
-class Post < ActiveRecord::Base
-  scope :user_posts_on_date, ->(date, options) {
-    where(user_id: options[:user_id], blog_id: options[:blog_id], date: date)
-  }
-end
-
-class UsersController < ApplicationController
-  include Sift
 
-  filter_on :user_posts_on_date, type: :scope, scope_params: [:user_id, :blog_id]
+  private
 
-  def show
-    render json: filtrate(Post.all)
+  def render_filter_errors
+    render json: { errors: filter_errors }, status: :bad_request
   end
 end
 ```
 
-Passing `?filters[user_posts_on_date]=10/12/20` will call the `user_posts_on_date` scope with
-`10/12/20` as the the first argument, and will grab the `user_id` and `blog_id` out of the params and pass them as a hash, as the second argument.
-
-### Renaming Filter Params
-
-A filter param can have a different field name than the column or scope. Use `internal_name` with the correct name of the column or scope.
-
-```ruby
-class PostsController < ApplicationController
-  include Sift
+Consumers can then filter and sort via query parameters:
 
-  filter_on :post_id, type: :int, internal_name: :id
-
-end
 ```
-
-### Filter on Ranges
-
-Some parameter types support ranges. Ranges are expected to be a string with the bounding values separated by `...`
-
-For example `?filters[price]=3...50` would return records with a price between 3 and 50.
-
-The following types support ranges
-
-- int
-- decimal
-- boolean
-- date
-- time
-- datetime
-
-### Mutating Filters
-
-Filters can be mutated before the filter is applied using the `tap` argument. This is useful, for example, if you need to adjust the time zone of a `datetime` range filter.
-
-```ruby
-
-class PostsController < ApplicationController
-  include Sift
-
-  filter_on :expiration, type: :datetime, tap: ->(value, params) {
-    value.split("...").
-      map do |str|
-        str.to_date.in_time_zone(LOCAL_TIME_ZONE)
-      end.
-      join("...")
-  }
-end
+GET /posts?filters[title]=hello&filters[priority]=1...5&sort=-published_at,title
 ```
 
-### Filter on jsonb column
-
-Usually JSONB columns stores values as an Array or an Object (key-value), in both cases the parameter needs to be sent in a JSON format
-
-**Array**
-
-It should be sent an array in the URL Query parameters
-
-- `?filters[metadata]=[1,2]`
-
-**key-value**
-
-It can be passed one or more Key values:
-
-- `?filters[metadata]={"data_1":"test"}`
-- `?filters[metadata]={"data_1":"test","data_2":"[1,2]"}`
-
-When the value is an array, it will filter records with those values or more, for example:
-
-- `?filters[metadata]={"data_2":"[1,2]"}`
-
-Will return records with next values stored in the JSONB column `metadata`:
-
-```ruby
-{ data_2: 1 }
-{ data_2: 2 }
-{ data_2: [1] }
-{ data_2: [2] }
-{ data_2: [1,2] }
-{ data_2: [1,2,3] }
-```
-
-When the `null` value is included in the array, it will return also all the records without any value in that property, for example:
-
-- `?filters[metadata]={"data_2":"[false,null]"}`
-
-Will return records with next values stored in the JSONB column `metadata`:
-
-```ruby
-{ data_2: null }
-{ data_2: false }
-{ data_2: [false] }
-{ data_1: {another: 'information'} } # When the JSONB key "data_2" is not set.
-```
-
-### Filter on JSON Array
-
-`int` type filters support sending the values as an array in the URL Query parameters. For example `?filters[id]=[1,2]`. This is a way to keep payloads smaller for GET requests. When URI encoded this will become `filters%5Bid%5D=%5B1,2%5D` which is much smaller the standard format of `filters%5Bid%5D%5B%5D=1&&filters%5Bid%5D%5B%5D=2`.
-
-On the server side, the params will be received as:
-
-```ruby
-# JSON array encoded result
-"filters"=>{"id"=>"[1,2]"}
-
-# standard array format
-"filters"=>{"id"=>["1", "2"]}
-```
-
-Note that this feature cannot currently be wrapped in an array and should not be used in combination with sending array parameters individually.
-
-- `?filters[id][]=[1,2]` => invalid
-- `?filters[id][]=[1,2]&filters[id][]=3` => invalid
-- `?filters[id]=[1,2]&filters[id]=3` => valid but only 3 is passed through to the server
-- `?filters[id]=[1,2]` => valid
-
-#### A note on encoding for JSON Array feature
-
-JSON arrays contain the reserved characters "`,`" and "`[`" and "`]`". When encoding a JSON array in the URL there are two different ways to handle the encoding. Both ways are supported by Rails.
-For example, lets look at the following filter with a JSON array `?filters[id]=[1,2]`:
-
-- `?filters%5Bid%5D=%5B1,2%5D`
-- `?filters%5Bid%5D%3D%5B1%2C2%5D`
-
-In both cases Rails will correctly decode to the expected result of
-
-```ruby
-{ "filters" => { "id" => "[1,2]" } }
-```
-
-### Sort Types
-
-Every sort must have a type, so that Sift knows what to do with it. The current valid sort types are:
-
-- int - Sort on an integer column
-- decimal - Sort on a decimal column
-- string - Sort on a string column
-- text - Sort on a text column
-- date - Sort on a date column
-- time - Sort on a time column
-- datetime - Sort on a datetime column
-- scope - Sort on an ActiveRecord scope
-
-### Sort on Scopes
-
-Just as your sort values are used to scope queries on a column, values you
-pass to a scope sort will be used as arguments to that scope. For example:
-
-```ruby
-class Post < ActiveRecord::Base
-  scope :order_on_body_no_params, -> { order(body: :asc) }
-  scope :order_on_body, ->(direction) { order(body: direction) }
-  scope :order_on_body_then_id, ->(body_direction, id_direction) { order(body: body_direction).order(id: id_direction) }
-end
-
-class PostsController < ApplicationController
-  include Sift
-
-  sort_on :order_by_body_ascending, internal_name: :order_on_body_no_params, type: :scope
-  sort_on :order_by_body, internal_name: :order_on_body, type: :scope, scope_params: [:direction]
-  sort_on :order_by_body_then_id, internal_name: :order_on_body_then_id, type: :scope, scope_params: [:direction, :asc]
-
-
-  def index
-    render json: filtrate(Post.all)
-  end
-end
-```
-
-`scope_params` takes an order-specific array of the scope's arguments. Passing in the param :direction allows the consumer to choose which direction to sort in (ex. `-order_by_body` will sort `:desc` while `order_by_body` will sort `:asc`)
-
-Passing `?sort=-order_by_body` will call the `order_on_body` scope with
-`:desc` as the argument. The direction is the only argument that the consumer has control over.
-Passing `?sort=-order_by_body_then_id` will call the `order_on_body_then_id` scope where the `body_direction` is `:desc`, and the `id_direction` is `:asc`. Note: in this example the user has no control over id_direction. To demonstrate:
-Passing `?sort=order_by_body_then_id` will call the `order_on_body_then_id` scope where the `body_direction` this time is `:asc`, but the `id_direction` remains `:asc`.
-
-Scopes that accept no arguments are currently supported, but you should note that the user has no say in which direction it will sort on.
-
-`scope_params` can also accept symbols that are keys in the `params` hash. The value will be fetched and passed on as an argument to the scope.
-
-## Consumer Usage
-
-Filter:
-`?filters[<field_name>]=<value>`
-
-Filters are translated to Active Record `where`s and are chained together. The order they are applied is not guarenteed.
-
-Sort:
-`?sort=-published_at,position`
-
-Sort is translated to Active Record `order` The sorts are applied in the order they are passed by the client.
-the `-` symbol means to sort in `desc` order. By default, keys are sorted in `asc` order.
-
 ## Installation
 
 Add this line to your application's Gemfile:
@@ -306,58 +54,20 @@ And then execute:
 $ bundle
 ```
 
-Or install it yourself as:
-
-```bash
-$ gem install procore-sift
-```
-
-## Without Rails
+## Documentation
 
-We have some future plans to remove the rails dependency so that other frameworks such as Sinatra could leverage this gem.
+- [Filters](docs/filters.md) - Filter types, scopes, ranges, JSONB, defaults, validation
+- [Sorts](docs/sorts.md) - Sort types and scope-based sorting
+- [Consumer API](docs/api.md) - Query parameter format for API consumers
+- [Contributing](docs/contributing.md) - Development setup and publishing
 
-## Contributing
+## Changelog
 
-Installing gems before running tests:
-
-```bash
-$ bundle exec appraisal install
-```
-
-Running tests:
-
-```bash
-$ bundle exec appraisal rake test
-```
-
-## Publishing
-
-Publishing is done use the `gem` commandline tool. You must have permissions to publish a new version. Users with permissions can be seen here https://rubygems.org/gems/procore-sift.
-
-When a bump is desired, the gemspec should have the version number bumped and merged into master.
-
-Step 1: build the new version
-`gem build sift.gemspec`
-
-```
-  Successfully built RubyGem
-  Name: procore-sift
-  Version: 0.14.0
-  File: procore-sift-0.14.0.gem
-```
-
-Step2: Push the updated build
-`gem push procore-sift-0.14.0.gem`
-
-```
-Pushing gem to https://rubygems.org...
-Successfully registered gem: procore-sift (0.14.0)
-```
+See [CHANGELOG.md](CHANGELOG.md) for release notes.
 
 ## License
 
-The gem is available as open source under the terms of the [MIT
-License](http://opensource.org/licenses/MIT).
+The gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).
 
 ## About Procore
 
@@ -371,5 +81,4 @@ The Procore Gem is maintained by Procore Technologies.
 
 Procore - building the software that builds the world.
 
-Learn more about the #1 most widely used construction management software at
-[procore.com](https://www.procore.com/)
+Learn more about the #1 most widely used construction management software at [procore.com](https://www.procore.com/)

data/lib/procore-sift.rb

@@ -66,8 +66,8 @@ module Sift
   end
 
   class_methods do
-    def filter_on(parameter, type:, internal_name: parameter, default: nil, validate: nil, scope_params: [], tap: nil)
-      filters << Filter.new(parameter, type, internal_name, default, validate, scope_params, tap)
+    def filter_on(parameter, type:, internal_name: parameter, default: nil, validate: nil, scope_params: [], tap: nil, allow_nil: false)
+      filters << Filter.new(parameter, type, internal_name, default, validate, scope_params, tap, allow_nil: allow_nil)
     end
 
     def filters

data/lib/sift/filter.rb

@@ -4,8 +4,8 @@ module Sift
   class Filter
     attr_reader :parameter, :default, :custom_validate, :scope_params
 
-    def initialize(param, type, internal_name, default, custom_validate = nil, scope_params = [], tap = ->(value, _params) { value })
-      @parameter = Parameter.new(param, type, internal_name)
+    def initialize(param, type, internal_name, default, custom_validate = nil, scope_params = [], tap = ->(value, _params) { value }, allow_nil: false)
+      @parameter = Parameter.new(param, type, internal_name, allow_nil: allow_nil)
       @default = default
       @custom_validate = custom_validate
       @scope_params = scope_params
@@ -41,7 +41,7 @@ module Sift
     end
 
     def type_validator
-      @type_validator ||= Sift::TypeValidator.new(param, type)
+      @type_validator ||= Sift::TypeValidator.new(param, type, allow_nil: parameter.allow_nil)
     end
 
     def type

data/lib/sift/filtrator.rb

@@ -46,7 +46,7 @@ module Sift
 
     def active_filters
       filters.select do |filter|
-        filter_params[filter.param].present? || filter.default || filter.always_active?
+        filter_params.include?(filter.param) || filter.default || filter.always_active?
       end
     end
   end

data/lib/sift/parameter.rb

@@ -1,12 +1,13 @@
 module Sift
   # Value Object that wraps some handling of filter params
   class Parameter
-    attr_reader :param, :type, :internal_name
+    attr_reader :param, :type, :internal_name, :allow_nil
 
-    def initialize(param, type, internal_name = param)
+    def initialize(param, type, internal_name = param, allow_nil: false)
       @param = param
       @type = type
       @internal_name = internal_name
+      @allow_nil = allow_nil
     end
 
     def parse_options

data/lib/sift/type_validator.rb

@@ -17,9 +17,10 @@ module Sift
                        :scope,
                        :jsonb].freeze
 
-    def initialize(param, type)
+    def initialize(param, type, allow_nil: false)
       @param = param
       @type = type
+      @allow_nil = allow_nil
     end
 
     attr_reader :param, :type
@@ -46,7 +47,7 @@ module Sift
     private
 
     def valid_int?
-      { valid_int: true }
+      @allow_nil ? { valid_int: { allow_null_token: true } } : { valid_int: true }
     end
   end
 end

data/lib/sift/validators/valid_int_validator.rb

@@ -1,4 +1,6 @@
 class ValidIntValidator < ActiveModel::EachValidator
+  NULL_TOKEN = "null"
+
   def validate_each(record, attribute, value)
     record.errors.add attribute, (options[:message] || "must be integer, array of integers, or range") unless
       valid_int?(value)
@@ -6,8 +8,12 @@ class ValidIntValidator < ActiveModel::EachValidator
 
   private
 
+  def allow_null_token?
+    options.fetch(:allow_null_token, false)
+  end
+
   def valid_int?(value)
-    integer_array?(value) || integer_or_range?(value)
+    (allow_null_token? && null_token?(value)) || integer_array?(value) || integer_or_range?(value)
   end
 
   def integer_array?(value)
@@ -15,10 +21,14 @@ class ValidIntValidator < ActiveModel::EachValidator
       value = Sift::ValueParser.new(value: value).array_from_json
     end
 
-    value.is_a?(Array) && value.any? && value.all? { |v| integer_or_range?(v) }
+    value.is_a?(Array) && value.any? && value.all? { |v| integer_or_range?(v) || (allow_null_token? && null_token?(v)) }
   end
 
   def integer_or_range?(value)
     !!(/\A\d+(...\d+)?\z/ =~ value.to_s)
   end
+
+  def null_token?(value)
+    value.to_s.downcase == NULL_TOKEN
+  end
 end

data/lib/sift/value_parser.rb

@@ -35,7 +35,7 @@ module Sift
       parsed_jsonb.each_with_object({}) do |key_value, hash|
         key   = key_value.first
         value = key_value.last
-        hash[key] = value.is_a?(String) ? parse_json(value) : value
+        hash[key] = parse_jsonb_value(value)
       end
     end
 
@@ -53,9 +53,25 @@ module Sift
     attr_reader :value, :type, :supports_boolean, :supports_json, :supports_json_object, :supports_ranges
 
     def parse_as_range?(raw_value=value)
+      # jsonb values must not be parsed as a top-level range: the outer value is
+      # a Hash (nested params) or a JSON object string, and any "..." range lives
+      # inside an individual key's value, which is handled by parse_jsonb_value.
+      return false if raw_value.is_a?(Hash) || supports_json_object
+
       supports_ranges && raw_value.to_s.include?("...")
     end
 
+    # Parses a single value from a jsonb object. A "..." string is converted into
+    # a Range (with its endpoints normalized to DateTimes where possible) so the
+    # range handling lives here rather than in WhereHandler; other strings may be
+    # nested JSON (e.g. an embedded array) and are parsed accordingly.
+    def parse_jsonb_value(raw_value)
+      return raw_value unless raw_value.is_a?(String)
+      return date_range(raw_value) if raw_value.include?("...")
+
+      parse_json(raw_value)
+    end
+
     def range_value
       Range.new(*value.split("..."))
     end
@@ -84,15 +100,18 @@ module Sift
       from_date_string, end_date_string = raw_value.split("...")
       return unless end_date_string
 
-      parsed_dates = [from_date_string, end_date_string].map do |date_string|
-        begin
-          DateTime.parse(date_string.to_s)
-        rescue StandardError
-          date_string
-        end
-      end
+      [from_date_string, end_date_string].map { |date_string| parse_date(date_string) }.join("...")
+    end
+
+    def date_range(raw_value)
+      from_date_string, end_date_string = raw_value.split("...")
+      Range.new(parse_date(from_date_string), parse_date(end_date_string))
+    end
 
-      parsed_dates.join("...")
+    def parse_date(date_string)
+      DateTime.parse(date_string.to_s)
+    rescue StandardError
+      date_string
     end
   end
 end

data/lib/sift/version.rb

@@ -1,3 +1,3 @@
 module Sift
-  VERSION = "1.0.0".freeze
+  VERSION = "1.2.0".freeze
 end

data/lib/sift/where_handler.rb

@@ -1,5 +1,7 @@
 module Sift
   class WhereHandler
+    NULL_TOKEN = "null"
+
     def initialize(param)
       @param = param
     end
@@ -7,6 +9,8 @@ module Sift
     def call(collection, value, _params, _scope_params)
       if @param.type == :jsonb
         apply_jsonb_conditions(collection, value)
+      elsif @param.allow_nil
+        apply_null_aware_conditions(collection, value)
       else
         collection.where(@param.internal_name => value)
       end
@@ -14,8 +18,23 @@ module Sift
 
     private
 
+    def apply_null_aware_conditions(collection, value)
+      values = Array(value)
+      has_null = values.any? { |v| v.to_s.downcase == NULL_TOKEN }
+      non_null_values = values.reject { |v| v.to_s.downcase == NULL_TOKEN }
+
+      if has_null && non_null_values.any?
+        collection.where(@param.internal_name => nil)
+                  .or(collection.where(@param.internal_name => non_null_values))
+      elsif has_null
+        collection.where(@param.internal_name => nil)
+      else
+        collection.where(@param.internal_name => value)
+      end
+    end
+
     def apply_jsonb_conditions(collection, value)
-      return collection.where("#{@param.internal_name} @> ?", val.to_s) if value.is_a?(Array)
+      return collection.where("#{@param.internal_name} @> ?", value.to_s) if value.is_a?(Array)
 
       value.each do |key, val|
         collection = if val.is_a?(Array)
@@ -26,6 +45,8 @@ module Sift
             "#{@param.internal_name}->>'#{key}' #{element === nil ? 'IS NULL' : "= :value_#{i}"}"
           end.join(' OR ')
           collection.where("(#{main_condition}) OR (#{sub_conditions})", elements)
+        elsif val.is_a?(Range)
+          collection.where("#{@param.internal_name}->>'#{key}' BETWEEN ? AND ?", val.first, val.last)
         else
           collection.where("#{@param.internal_name}->>'#{key}' = ?", val.to_s)
         end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: procore-sift
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.2.0
 platform: ruby
 authors:
 - Procore Technologies
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2023-04-03 00:00:00.000000000 Z
+date: 2026-07-15 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activerecord
@@ -16,16 +16,16 @@ dependencies:
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '6.1'
+        version: '7.2'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '6.1'
+        version: '7.2'
 - !ruby/object:Gem::Dependency
-  name: pry
+  name: appraisal
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
@@ -39,21 +39,21 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
-  name: rails
+  name: minitest
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - "<"
       - !ruby/object:Gem::Version
-        version: '6.1'
+        version: '6'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - "<"
       - !ruby/object:Gem::Version
-        version: '6.1'
+        version: '6'
 - !ruby/object:Gem::Dependency
-  name: rake
+  name: pry
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
@@ -67,21 +67,21 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
-  name: rubocop
+  name: rails
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '='
+    - - ">="
       - !ruby/object:Gem::Version
-        version: 0.71.0
+        version: '7.0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '='
+    - - ">="
       - !ruby/object:Gem::Version
-        version: 0.71.0
+        version: '7.0'
 - !ruby/object:Gem::Dependency
-  name: sqlite3
+  name: rake
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
@@ -95,7 +95,21 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
-  name: appraisal
+  name: rubocop
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.68'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.68'
+- !ruby/object:Gem::Dependency
+  name: sqlite3
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
@@ -108,14 +122,14 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: '0'
-description: Easily write arbitrary filters
+description: A declarative DSL for building filters and sorts with Rails and Active
+  Record
 email:
 - dev@procore.com
 executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- MIT-LICENSE
 - README.md
 - Rakefile
 - lib/procore-sift.rb
@@ -137,7 +151,8 @@ files:
 homepage: https://github.com/procore/sift
 licenses:
 - MIT
-metadata: {}
+metadata:
+  allowed_push_host: https://rubygems.org
 post_install_message:
 rdoc_options: []
 require_paths:
@@ -146,15 +161,15 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: 2.7.0
+      version: 3.3.0
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.4.8
+rubygems_version: 3.5.22
 signing_key:
 specification_version: 4
-summary: Summary of Sift.
+summary: Build dynamic filters and sorts for Rails and Active Record
 test_files: []

data/MIT-LICENSE

@@ -1,20 +0,0 @@
-Copyright 2016 Adam Hess
-
-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.