Skip to content
REST in Peace
Find file
Pull request Compare This branch is 36 commits ahead, 1 commit behind acidlabs:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


Build Status

REST in Peace is a library for RESTful applications.


Add the following dependency to your project.clj file:

[rip "0.1.1"]


Named Routes

The main idea behind RIP's routing system is a thin layer over compojure that provides named routes to facilitate their construction, allowing more control over a set of routes, and also include some reverse routing functionality.

(use 'rip.core)

;; Single named route
(defroute home :get "/" [] "welcome")

;; Named nested routes
(defscope api

  ;; Actions can be defined using GET, POST, etc.
  ;; A name must be provided for wrappers and reverse routing
  ;; GET /api
  (GET :home [] ...)

  ;; Use a map instead of a keyword to specify a path
  ;; GET /api/about
  (GET {:name :about :path "/about"} [] ...)

  ;; Include other actions with a default path

    ;; GET /api/v1
    (GET :v1 [] ...))

  ;; Nest other scopes or resources

    ;; Resources are scopes with path "/{resource-name}", check also 'defresource'
      ;; Rip includes some default actions like:
      ;;   index   => GET    /
      ;;   make    => POST   /
      ;;   show    => GET    /:id
      ;;   change  => PUT    /:id
      ;;   destroy => DELETE /:id
      ;; Examples:
      (index [] ...)
      (change [id] ...)

      ;; Include other actions with default /:id path
      ;; Same as using (include "/:id" ...)
       ;; PATCH /api/users/:id/activate
       (PATCH {:name :activate :path "/activate"} [id] ...))

  ;; Nest resources passing the member key

      ;; GET /api/users/:user-id/documents
      (index [user-id] ...))))))

;; Reverse Routing
(defroute paths :get "/paths"
  (path-for :home)
  ;; => "/"

  (path-for :api [:v1])
  ;; => "/api/v1"

  (path-for :api [:users :show] 1)
  ;; => "/api/users/1"

  (path-for :api [:users :documents :index] 1 {:page 10})
  ;; => "/api/users/1/documents?page=10"

  (link-for :api [:users :show] 1)
  ;; => {:href "/api/users/1" :method "GET"}

  (url-for :api [:about])
  ;; => "http://{hostname}/api/about"

;; Generate a single handler and add a middleware for path-for, link-for and url-for usage.
(routes-for home api paths)

;; path-for, link-for and url-for work only in a handler of a route compiled using routes-for.


Use the wrap function to add middleware to the actions inside a scope. Wrap takes a wrapping function similiar to ring's middleware, this function only takes a handler and returns another handler. Every use of wrap will be stacked and later applied when the scope is compiled to a handler. If necessary, a before-wrap and after-wrap functions are provided for middleware applying order.

(use 'rip.core)

(defresources posts
  ;; adds a named middleware to all the actions defined in the scope
  (wrap -wrapper- {:name :wrap1})

  (show [id] ...)
  (change [id post] ...)

  ;; adds middleware before the :response wrapper
  (before-wrap :wrap1 -wrapper- {:name :wrap2 :only [:show :change]})

  ;; adds middleware after the :exists? wrapper
  (after-wrap :wrap2 -wrapper- {:except [:show]}))


The concept of validator is an abstraction for validating clojure's maps. They are intended to represent most of the validation process of an application. They are very extendable, composable and can be used for APIs or web forms validations.

(use 'rip.validation)

;; Define a validator
(defvalidator user
  ;; Add a field
  (field :name)

  ;; Specify the parser to be applied to a field with the parse-to function.
  ;; In case the parser fails, a type error will be added to the validation.
  ;; Default types :int :double :float :boolean :long :bigint :bigdecimal :uuid
  (field :age (parse-to :int))

  ;; Custom parsers can also be passed to the parse-to function
  (field :birthday (parse-to #(if % (java.sql.Date/valueOf %))))

  ;; Add constraints like 'required' or custom validations using the validates function
  ;; validates requires a predicate function and an optional message
  (field :email 
         (validates (fn [email] (boolean (re-matches #".+\@.+\..+" email)))
         "invalid format"))

  ;; Message can also be a map in case you want to specify an error code for your API
  (field :password required (validates (min-length 6) {:code 123 :message "too short"}))  

  (field :password-confirmation required)

  ;; Include global validations
   (fn [user] (= (:password user) (:password-confirmation user)))
   "Password confirmation doesn't match confirmation")

  ;; Add more constraints to fields
  (constraint :name required)

  ;; Set required fields
  (required-fields [:password :password-confirmation])

  ;;Nest validators
  (assoc-one :address
      (field :street))
    {:required true})

  (assoc-many :documents
      (field :name))))

;; Validate using the validate function
(def validation (validate user {:email ""}))
;; => {:valid? false 
;;     :value  {:email ""} 
;;     :errors [{:field :password :message "Can't be blank"}]}

;; Use if-valid for binding and if-else expressions
(if-valid validation
  ;; bind a vector  of the form [value errors].
  [{name :name} err]
  ;; if else expressions
Something went wrong with that request. Please try again.