Querifier
Querifier is a gem intended to create queries for api's easy & fast, it isn't an ORM, instead, it's a layer over it.
The basic use case is when you have an API and you want to filter & order the results without having to think too much
Demo
You can check https://querifier-demo.herokuapp.com/v1/books?page=1&filter[where][title]=Season&filter[order][id]=desc for a demo of how it works
The source code of the demo is available at https://github.com/hdf1986/querifier-demo
Installation
Add this line to your application's Gemfile:
gem 'querifier'
And then execute:
bundle
If you are using rails, you can do:
rails generate querifier:install
Usage
If you are using rails, you can do:
rails generate querifier:query your_model
it will create a query for your model, in this case it will be
class BookQuery
include Querifier::Queries::Default
# If no order param is provided, then this order will be used
# default_sort { id: :asc }
# Configure these constants to add attributes to the ordering a filtering
where_attributes :id # Configure your attributes here
order_attributes :id # Configure your attributes here
end
After that, your query will be able to receive params like this
# Will return an array or query with the filtered and ordered results
BookQuery.new(filter: { order: { id: desc }, where: { id: 1 } }).collection
This work great with Rails controllers, you can start filtering and ordering with something like this:
class BookController < ApiController
def index
render json: BookQuery.new(params).collection
end
end
Custom model class
Querifier will try to assume the class for your model removing the Query
from your query classname, some examples are:
- BookQuery => Book
- BooksQuery => Books
- SomeModule::BookQuery => Book
If your model isn't called like your query, you can configure it with the entity_class method, something like:
class BookQuery
include Querifier::Queries::Default
# If no order param is provided, then this order will be used
# default_sort { id: :asc }
# Configure these constants to add attributes to the ordering a filtering
where_attributes :id, :author_name # Configure your attributes here
order_attributes :id # Configure your attributes here
# This will replace the assumption with the class you send via parameter
# The :: are optional, but I recommend you to be explicit about the modules of your class
def self.default_collection
::SomeOtherClassName.all
end
def (value)
@collection = @collection.joins(:author).where(authors: { name: value })
end
end
Custom methods
In case you arrive to a case where you need a filter different than the default ones, you can do something like this:
class BookQuery
include Querifier::Queries::Default
# If no order param is provided, then this order will be used
# default_sort { id: :asc }
# Configure these constants to add attributes to the ordering a filtering
where_attributes :id, :author_name # Configure your attributes here
order_attributes :id # Configure your attributes here
def (value)
@collection = @collection.joins(:author).where(authors: { name: value })
end
end
You can do the same with the ordering
class BookQuery
include Querifier::Queries::Default
# If no order param is provided, then this order will be used
# default_sort { id: :asc }
# Configure these constants to add attributes to the ordering a filtering
where_attributes :id, :author_name # Configure your attributes here
order_attributes :id # Configure your attributes here
def (direction)
@collection = @collection.joins(:author).order("authors.name #{direction}")
# Don't pannic! I know we are concatenating a raw value to the query, but in this case this is being validated in the invocation of this method
# In case you have any doubt about it, check https://github.com/hdf1986/querifier/blob/master/lib/querifier/queries/order.rb valid_sort? method
# Im totally open to better ways of doing this, since i didn't find a nice way to implement joined and dinamic ordering queries
end
end
Good to know
- You can create a filter_by_* or order_by_* method for any name you want to, just take care that if it doesn't exist in the database, it will need a custom method as seen before
- The filters are executed in the order they are received from the
.new
method, this is a coincidence, so i can't ensure it will keep happening in the future - Most of this structure is inspired by Loopback REST API for querying data (see https://loopback.io/doc/en/lb3/Querying-data.html). I don't like loopback at all, but i think this standard is a good place to start with
- Probably there's some minor performance differences between custom methods and default ones (the custom ones being the faster ones), because we use
method_missing
magic to implement the default ones - If you don't want to use where, or order, you can include just
Querifier::Queries::Order
orQuerifier::Queries::Where
instead ofQuerifier::Queries::Default
, according to your needs
To-do's
- Support for greather than where filter
- Support for lower than where filter
- Support for equal than where filter (currently we are using sql LIKE by default)
- Performance metrics
- Permit multiple order attributes: We are supporting this in the structure, but in the practice we are ignoring the second or greather elements
- Add support for different adapters: Currently we are assuming that the ORM is something similar to ActiveRecord, i don't think it's a good idea to be tied to ActiveRecord, so will be great to provide some sort of customizable things there
Development
After checking out the repo, run bin/setup
to install dependencies. Then, run rake spec
to run the tests. You can also run bin/console
for an interactive prompt that will allow you to experiment.
Contributing
Bug reports and pull requests are welcome on GitHub at https://github.com/hdf1986/querifier. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.
License
The gem is available as open source under the terms of the MIT License.
Code of Conduct
Everyone interacting in the Querifier project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.