comply 1.7.0 → 1.9.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: f2093d423f8fa4b54e49b7122e1ea13c93aa7b2a
-  data.tar.gz: 87d69cb316312e9a4d34754e3ae2822c3b6468f6
+  metadata.gz: 6baf5ccbed26227f68924f4fd6e771212d5453f8
+  data.tar.gz: a9f6ad3d2403b258a0b6474c84ff106730424143
 SHA512:
-  metadata.gz: 07d31a395dbf14779c2055b78feabdfce488b2a6fa9a40a52ed62317e40d119719fb4c5bd3a404f6899b42a72b7bfa71efeda7f8a6fce80954a67646427b90d2
-  data.tar.gz: 4841e13268f817816b740765004280724a9289d20cfa8e5d857f7f8c70e997f67880d5bd1957b220e6abd0a8b162a56d4eeae01653a3dabd40f9c0bbc750967d
+  metadata.gz: d2d121eafee9f87871559812c2d5b77fba805a91adcbd2fbb8271799a1612afac796823ac4b67cf9ff2dee6e6627fb745f7ea846457e43930aa452eb24b72bcd
+  data.tar.gz: f2fc14f21bf83e8fb8dbd94dce17e8ec3ac6a92eb7db0df0fc1e7e18b6d1173e9f5b5e6f2649e9346b391b93a83b2659f81ee0a945a342e46e5e38266bb2dbc4

data/README.md

@@ -68,6 +68,45 @@ Want success messages to add some personality to your forms? Add the message as
 <%= f.text_field :title, data: { validate: true, validate_success: "Sweet title yo!" } %>
 ```
 
+### Validation contexts
+Supplementary reading on validation contexts:
+- [ActiveRecord Validations :on](http://guides.rubyonrails.org/active_record_validations.html#on)
+- [Also see api.rubyonrails.org](http://api.rubyonrails.org/classes/ActiveRecord/Validations.html#method-i-valid-3F)
+- [Mastering Rails Validations: Contexts](http://blog.arkency.com/2014/04/mastering-rails-validations-contexts/)
+
+By default, all validations run through Comply's `Comply::ValidationsController` will be in the `:comply` validation
+context. This gives you the option to modify how your application runs its validations. The most common way to use
+validation contexts, is when you want to skip a certain validation. Let's say we didn't want to check the uniqueness
+of a particular attribute when asking Comply to validate a model. You would do this:
+
+```ruby
+class SomeModel < ActiveRecord::Base
+  validates :my_attribute, uniqueness: true, unless: -> { validation_context == :comply }
+  # or perhaps you *ONLY* want to run the validation when in the :comply context
+  validates :other_attribute, numericality: true, on: :comply
+end
+```
+
+You now have the option to specify your own context if you inherit from `Comply::ValidationsController` if your
+model has a specific business case for needing to run/not-run a set of validations for a given context.
+
+```ruby
+class SomeController < Comply::ValidationsController
+  # ... snip
+  protected
+
+  def validation_context
+    :my_new_context
+  end
+end
+
+class SomeModel
+  validates :my_attribute, uniqueness: true, unless: -> { validation_context == :my_new_context }
+end
+```
+
+That's it!
+
 ### Event triggers
 You can change the jQuery event which triggers the input validation with the `data-validate-event` attribute.
 ```erb

data/app/assets/javascripts/comply/base_validatable_form.js.coffee

@@ -14,7 +14,7 @@ class Comply.BaseValidatableForm
     @validate inputs: @inputs, submit: true
 
   validate: (options) ->
-    $.get @validationRoute, @_params(), (response) =>
+    $.post @validationRoute, @_params(), (response) =>
       @_onValidate(response, options)
 
       if @_allSuccess(response)

data/app/controllers/comply/validations_controller.rb

@@ -12,11 +12,18 @@ module Comply
     end
 
     def show
+      ActiveSupport::Deprecation.warn('GET support going away: use POST to access this endpoint') if request.request_method == 'GET'
       @instance = validation_instance
-      @instance.valid?(:comply)
+      @instance.valid?(validation_context)
       render json: { error: @instance.errors }
     end
 
+    protected
+
+    def validation_context
+      :comply
+    end
+
     private
 
     def validation_instance

data/config/routes.rb

@@ -1,5 +1,5 @@
 Comply::Engine.routes.draw do
-  match '/validations' => 'validations#show', via: [:get]
+  match '/validations' => 'validations#show', via: [:get, :post]
   # allow CORS requests
   match 'validations', via: [:options], to: proc { [200, {}, ['']] }
 end

data/lib/comply/version.rb

@@ -1,3 +1,3 @@
 module Comply
-  VERSION = '1.7.0'
+  VERSION = '1.9.0'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: comply
 version: !ruby/object:Gem::Version
-  version: 1.7.0
+  version: 1.9.0
 platform: ruby
 authors:
 - "@jacobaweiss"
@@ -12,7 +12,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-08-19 00:00:00.000000000 Z
+date: 2016-10-10 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: coffee-rails
@@ -128,8 +128,9 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.2.3
+rubygems_version: 2.2.5
 signing_key: 
 specification_version: 4
 summary: Inline validation of your ActiveRecord models via the AJAX internets
 test_files: []
+has_rdoc: