parse-stack 1.4.3 → 1.5.1

data/README.md

@@ -19,20 +19,15 @@ Or install it yourself as:
 
     $ gem install parse-stack
 
+### Rack / Sinatra
+Parse-Stack API, models and webhooks easily integrate in your existing Rack/Sinatra based applications. For more details see [Parse-Stack Rack Example](https://github.com/modernistik/parse-stack-example).
+
 ### Rails
 Parse-Stack comes with support for Rails by adding additional rake tasks and generators. After adding `parse-stack` as a gem dependency in your Gemfile and running `bundle`, you should run the install script:
 
     $ rails g parse_stack:install
 
-This will create a configuration file (`config/initializers/parse.rb`) and a set of sample models and hooks under `app/models` directory. Modify `config/initializers/parse.rb` file with your Parse-Server API keys. You can then generate models with the `parse_stack:model` generator.
-
-    $ rails g parse_stack:model Song name:string released:date genres:array
-
-This would create a `song.rb` file in `app/models` with the provided properties. Once you are ready to update your schema, you can run the `parse:upgrade` task to upgrade the remote Parse-Server schema to match your new models.
-
-    $ rails parse:upgrade
-
-That should create the new collection `Song` in your Parse-Server backend. For a more full featured example, see [Parse-Server-Rails-Example](https://github.com/modernistik/parse-server-rails-example).
+For a more details on the rails integration see [Parse-Stack Rails Example](https://github.com/modernistik/parse-stack-rails-example).
 
 ## Table Of Contents
 <!-- START doctoc generated TOC please keep comment here to allow auto update -->
@@ -40,7 +35,6 @@ That should create the new collection `Song` in your Parse-Server backend. For a
 
 
 - [Overview](#overview)
-- [Main Features](#main-features)
 - [Architecture](#architecture)
   - [Parse::Client](#parseclient)
   - [Parse::Query](#parsequery)
@@ -57,17 +51,40 @@ That should create the new collection `Song` in your Parse-Server backend. For a
   - [Parse::GeoPoint](#parsegeopoint)
     - [Calculating Distances between locations](#calculating-distances-between-locations)
   - [Parse::Bytes](#parsebytes)
-  - [Parse::User](#parseuser)
-  - [Parse::Installation](#parseinstallation)
+  - [Parse::ACL](#parseacl)
   - [Parse::Session](#parsesession)
+  - [Parse::Installation](#parseinstallation)
   - [Parse::Role](#parserole)
+  - [Parse::User](#parseuser)
+    - [Signup](#signup)
+      - [Third-Party Services](#third-party-services)
+    - [Login and Sessions](#login-and-sessions)
+    - [Linking and Unlinking Users](#linking-and-unlinking-users)
+    - [Request Password Reset](#request-password-reset)
 - [Modeling and Subclassing](#modeling-and-subclassing)
   - [Defining Properties](#defining-properties)
     - [Accessor Aliasing](#accessor-aliasing)
     - [Property Options](#property-options)
+      - [`:required`](#required)
+      - [`:field`](#field)
+      - [`:default`](#default)
+      - [`:alias`](#alias)
+      - [`:symbolize`](#symbolize)
+      - [`:enum`](#enum)
+      - [`:scope`](#scope)
   - [Associations](#associations)
     - [Belongs To](#belongs-to)
-    - [Has Many (Array or Relation)](#has-many-array-or-relation)
+      - [Options](#options)
+        - [`:required`](#required-1)
+        - [`:as`](#as)
+        - [`:field`](#field-1)
+    - [Has One](#has-one)
+    - [Has Many](#has-many)
+      - [Query](#query)
+      - [Array](#array)
+      - [Parse Relation](#parse-relation)
+      - [Options](#options-1)
+        - [`:through`](#through)
 - [Creating, Saving and Deleting Records](#creating-saving-and-deleting-records)
   - [Create](#create)
   - [Saving](#saving)
@@ -114,9 +131,10 @@ That should create the new collection `Song` in your Parse-Server backend. For a
     - [Bounding Box Constraint](#bounding-box-constraint)
   - [Relational Queries](#relational-queries)
   - [Compound Queries](#compound-queries)
+- [Query Scopes](#query-scopes)
 - [Calling Cloud Code Functions](#calling-cloud-code-functions)
 - [Calling Background Jobs](#calling-background-jobs)
-- [Model Callbacks](#model-callbacks)
+- [Active Model Callbacks](#active-model-callbacks)
 - [Schema Upgrades and Migrations](#schema-upgrades-and-migrations)
 - [Push Notifications](#push-notifications)
 - [Cloud Code Webhooks](#cloud-code-webhooks)
@@ -140,9 +158,13 @@ require 'parse/stack'
 
 Parse.setup app_id: APP_ID,
             api_key: REST_API_KEY,
+            master_key: YOUR_MASTER_KEY,
             server_url: 'https://api.parse.com/1/'
 
-# Object Mapper
+# login
+user = Parse::User.login(username, passwd)
+
+# Custom Subclasses
 class Song < Parse::Object
   property :name
   property :play, :integer
@@ -157,12 +179,17 @@ end
 class Artist < Parse::Object
   property :name
   property :genres, :array
+  has_many :fans, as: :user
+  has_one :manager, as: :user
+
+  scope :recent, ->(x) { query(:created_at.after => x) }
 end
 
 # updates schemas for your Parse app based on your models (non-destructive)
 Parse.auto_upgrade!
 
 artist = Artist.new(name: "Frank Sinatra", genres: ["swing", "jazz"])
+artist.fans << user
 artist.save
 
 # Query
@@ -192,21 +219,6 @@ result = Parse.call_function :myFunctionName, {param: value}
 
 ```
 
-## Main Features
-While there are many additional features of the framework, these are the main points.
-
-- Support for all Parse Query constraints.
-- Object Relational Mapping with dirty tracking.
-- Easy management of Parse GeoPoints, Files and ACLs.
-- Parse Queries support with caching middleware. (Reduces API usage)
-- Support for all Parse data types.
-- One-to-One, One-to-Many and Many-to-Many relations.
-- Integration with Parse Cloud Code Webhooks.
-- Send Push notifications with advanced targeting.
-- Schema upgrades and migrations.
-- Rake tasks for webhook registrations.
-- Some special magic with :save_all and :max limit fetch.
-
 ## Architecture
 The architecture of `Parse::Stack` is broken into four main components.
 
@@ -220,7 +232,7 @@ This class implements the [Parse REST Querying](https://parse.com/docs/rest/guid
 This component is main class for all object relational mapping subclasses for your application. It provides features in order to map your remote Parse records to a local ruby object. It implements the Active::Model interface to provide a lot of additional features, CRUD operations, querying, including dirty tracking, JSON serialization, save/destroy callbacks and others. While we are overlooking some functionality, for simplicity, you will mainly be working with Parse::Object as your superclass. While not required, it is highly recommended that you define a model (Parse::Object subclass) for all the Parse classes in your application.
 
 ### Parse::Webhooks
-Parse provides a feature called [Cloud Code Webhooks](http://blog.parse.com/announcements/introducing-cloud-code-webhooks/). For most applications, save/delete triggers and cloud functions tend to be implemented by Parse's own hosted Javascript solution called Cloud Code. However, Parse provides the ability to have these hooks utilize your hosted solution instead of their own, since their environment is limited in terms of resources and tools. If you are using the open source [Parse Server](https://github.com/ParsePlatform/parse-server), you must enable this hooks feature by enabling the environment variable `PARSE_EXPERIMENTAL_HOOKS_ENABLED` on your Parse server.
+Parse provides a feature called [Cloud Code Webhooks](http://blog.parse.com/announcements/introducing-cloud-code-webhooks/). For most applications, save/delete triggers and cloud functions tend to be implemented by Parse's own hosted Javascript solution called Cloud Code. However, Parse provides the ability to have these hooks utilize your hosted solution instead of their own, since their environment is limited in terms of resources and tools.
 
 ## Field Naming Conventions
 By convention in Ruby (see [Style Guide](https://github.com/bbatsov/ruby-style-guide#snake-case-symbols-methods-vars)), symbols and variables are expressed in lower_snake_case form. Parse, however, prefers column names in **lower-first camel case** (ex. `objectId`, `createdAt` and `updatedAt`). To keep in line with the style guides between the languages, we do the automatic conversion of the field names when compiling the query. As an additional exception to this rule, the field key of `id` will automatically be converted to the `objectId` field when used. If you do not want this to happen, you can turn off or change the value `Parse::Query.field_formatter` as shown below. Though we recommend leaving the default `:columnize` if possible.
@@ -266,8 +278,8 @@ If you wish to add additional connection middleware to the stack, you may do so
 Calling `setup` will create the default `Parse::Client` session object that will be used for all models and requests in the stack. You may retrive this client by calling the class `session()` method. It is possible to create different client connections and have different models point to different Parse applications and endpoints at the same time.
 
 ```ruby
-  default_client = Parse::Client.session(:default)
-  # or just Parse::Client.session
+  default_client = Parse::Client.client(:default)
+                   # alias Parse::Client.client
 ```
 
 ### Connection Options
@@ -301,7 +313,7 @@ Sets the default cache expiration time (in seconds) for successful non-empty `GE
 You may pass a hash of options that will be passed to the `Faraday` constructor.
 
 ## Parse Config
-Getting your configuration variables once you have a default client setup can be done with `Parse.config`. The first time this method is called, Parse-Stack will get the configuration from Parse-Server, and cache it. To force a reload of the config, use `config!`.
+Getting your configuration variables once you have a default client setup can be done with `Parse.config`. The first time this method is called, Parse-Stack will get the configuration from Parse-Server, and cache it. To force a reload of the config, use `config!`. You
 
 ```ruby
   Parse.setup( ... )
@@ -309,6 +321,12 @@ Getting your configuration variables once you have a default client setup can be
   val = Parse.config["myKey"]
   val = Parse.config["myKey"] # cached
 
+  # update a config with Parse
+  Parse.set_config "myKey", "someValue"
+
+  # batch update several
+  Parse.update_config({fieldEnabled: true, searchMiles: 50})
+
   # Force fetch of config!
   val = Parse.config!["myKey"]
 
@@ -327,12 +345,16 @@ end
 
 class Commentary < Parse::Object
   parse_class "Comment"
-	belongs_to :post 	
+	belongs_to :post
 	#'Author' class not defined locally
 	belongs_to :author
 end
 
 comment = Commentary.first
+comment.post? # true because it is non-nil
+comment.artist? # true because it is non-nil
+
+# both are true because they are in a Pointer state
 comment.post.pointer? # true
 comment.author.pointer? # true
 
@@ -341,6 +363,10 @@ comment.post # <Post @parse_class="Post", @id="xdqcCqfngz">
 
  # we have not defined an Author class handler
 comment.author # <Parse::Pointer @parse_class="Author", @id="hZLbW6ofKC">
+
+
+comment.post.fetch # fetch the relation
+comment.post.pointer? # false, it is now a full object.
 ```
 
 The effect is that for any unknown classes that the framework encounters, it will generate Parse::Pointer instances until you define those classes with valid properties and associations. While this might be ok for some classes you do not use, we still recommend defining all your Parse classes locally in the framework.
@@ -368,7 +394,7 @@ This class represents a Parse file pointer. `Parse::File` has helper methods to
 
 ```
 
-The default MIME type for all files is `iamge/jpeg`. This can be default can be changed by setting a value to `Parse::File.default_mime_type`. Other ways of creating a `Parse::File` are provided below. The created Parse::File is not uploaded until you call `save`.
+The default MIME type for all files is `image/jpeg`. This can be default can be changed by setting a value to `Parse::File.default_mime_type`. Other ways of creating a `Parse::File` are provided below. The created Parse::File is not uploaded until you call `save`.
 
 ```ruby
   # urls
@@ -418,15 +444,15 @@ This class manages the GeoPoint data type that Parse provides to support geo-que
 We include helper methods to calculate distances between GeoPoints: `distance_in_miles` and `distance_in_km`.
 
 ```ruby
-san_diego = Parse::GeoPoint.new(32.8233, -117.6542)
-los_angeles = Parse::GeoPoint.new [34.0192341, -118.970792]
+	san_diego = Parse::GeoPoint.new(32.8233, -117.6542)
+	los_angeles = Parse::GeoPoint.new [34.0192341, -118.970792]
 
-# Haversine calculations
-san_diego.distance_in_miles(los_angeles)
-# ~112.33 miles
+	# Haversine calculations
+	san_diego.distance_in_miles(los_angeles)
+	# ~112.33 miles
 
-san_diego.distance_in_km(los_angeles)
-# ~180.793 km
+	san_diego.distance_in_km(los_angeles)
+	# ~180.793 km
 ```
 
 ### Parse::Bytes
@@ -441,18 +467,72 @@ The `Bytes` data type represents the storage format for binary content in a Pars
   decoded = bytes.decoded # same as Base64.decode64
 ```
 
-### Parse::User
-This class represents the data and columns contained in the standard Parse `_User` collection. You may add additional properties and methods to this class. It is defined as follows:
+### Parse::ACL
+The `ACL` class represents the access control lists for each record. An ACL is represented by a JSON object with the keys being `Parse::User` object ids or the special key of `*`, which indicates the public access permissions.
+The value of each key in the hash is a `Parse::ACL::Permission` object which defines the boolean permission state for `read` and `write`.
+
+The example below illustrates a Parse ACL JSON object where there is a public read permission, but public write is prevented. In addition, the user with id `3KmCvT7Zsb`, is allowed to both read and write this record.
+
+```json
+{
+  "*": { "read": true },
+  "3KmCvT7Zsb": {  "read": true, "write": true }
+}
+```
+
+All `Parse::Object` subclasses have an `acl` property by default. With this property, you can apply and delete permissions for this particular Parse object record.
 
 ```ruby
-class Parse::User < Parse::Object
-  property :auth_data, :object
-  property :email
-  property :password
-  property :username
+  user = Parse::User.first
+  artist = Artist.first
+
+  artist.acl # "*": { "read": true, "write": true }
+
+  # apply public read, but no public write
+  artist.acl.everyone true, false
+
+
+  # allow user to have read and write access
+  artist.acl.apply user.id, true, true
+
+  # remove all permissions for this user id
+  artist.acl.delete user.id
+
+  # allow the 'Admins' role read and write
+  artist.acl.apply_role "Admins", true, true
+
+  artist.save
+```
+
+For more information about Parse record ACLs, see the documentation at  [Security](https://parseplatform.github.io/docs/rest/guide/#security)
+
+### Parse::Session
+This class represents the data and columns contained in the standard Parse `_Session` collection. You may add additional properties and methods to this class. It is defined as follows:
+
+```ruby
+class Parse::Session < Parse::Object
+  property :created_with, :object
+  property :expires_at, :date
+  property :installation_id
+  property :restricted, :boolean
+  property :session_token
+
+  belongs_to :user
 end
 ```
 
+You can get a specific `Parse::Session` given a session_token by using the `session` method. You can also find the user tied to a specific Parse session or session token with `Parse::User.session`.
+
+```ruby
+session = Parse::Session.session(token)
+
+session.user # the Parse user for this session
+
+# or fetch user with a session token
+user = Parse::User.session(token)
+
+```
+
 ### Parse::Installation
 This class represents the data and columns contained in the standard Parse `_Installation` collection. You may add additional properties and methods to this class. It is defined as follows:
 
@@ -475,21 +555,6 @@ class Parse::Installation < Parse::Object
 end
 ```
 
-### Parse::Session
-This class represents the data and columns contained in the standard Parse `_Session` collection. You may add additional properties and methods to this class. It is defined as follows:
-
-```ruby
-class Parse::Session < Parse::Object
-  property :created_with, :object
-  property :expires_at, :date
-  property :installation_id
-  property :restricted, :boolean
-  property :session_token
-
-  belongs_to :user
-end
-```
-
 ### Parse::Role
 This class represents the data and columns contained in the standard Parse `_Role` collection. You may add additional properties and methods to this class. It is defined as follows:
 
@@ -502,6 +567,115 @@ class Parse::Role < Parse::Object
 end
 ```
 
+### Parse::User
+This class represents the data and columns contained in the standard Parse `_User` collection. You may add additional properties and methods to this class. It is defined as follows:
+
+```ruby
+class Parse::User < Parse::Object
+  property :auth_data, :object
+  property :email
+  property :username
+
+end
+```
+
+While `:password` is a property on the User class, which will generally be empty whenever fetching User records.
+
+#### Signup
+You can signup new users in two ways. You can either use a class method `Parse::User.signup` to create a new user with the minimum fields of username, password and email, or create a `Parse::User` object can call the `signup!` method. If signup fails, it will raise the corresponding exception.
+
+```ruby
+user = Parse::User.signup(username, password, email)
+
+#or
+user = Parse::User.new username: "user", password: "s3cret"
+user.signup!
+```
+
+##### Third-Party Services
+You can signup users using third-party services like Facebook and Twitter as described in: [Signing Up and Logging In](https://parseplatform.github.io/docs/rest/guide/#signing-up-and-logging-in). To do this with Parse-Stack, you can call the `Parse::User.autologin_service` method by passing the service name and the corresponding authentication hash data. For a listing of supported third-party authentication services, see [OAuth](https://github.com/ParsePlatform/parse-server/wiki/OAuth).
+
+```ruby
+fb_auth = {}
+fb_auth[:id] = "123456789"
+fb_auth[:access_token] = "SaMpLeAAiZBLR995wxBvSGNoTrEaL"
+fb_auth[:expiration_date] = "2025-02-21T23:49:36.353Z"
+
+# signup or login a user with this auth data.
+user = Parse::User.autologin_service(:facebook, fb_auth)
+```
+
+You may also combine both approaches of signing up a new user with a third-party service and set additional custom fields. For this, use the method `Parse::User.create`.
+
+```ruby
+# or to signup a user with additional data, but linked to Facebook
+data = {
+  username: "johnsmith",
+  name: "John",
+  email: "user@example.com",
+  authData: { facebook: fb_auth }
+}
+user = Parse::User.create data
+```
+
+#### Login and Sessions
+With the `Parse::User` class, you can also perform login and logout functionality. The class special accessors for `session_token` and `session` to manage its authentication state. This will allow you to authenticate users as well as perform Parse queries as a specific user using their session token. To login a user, use the `Parse::User.login` method by supplying the corresponding username and password, or if you already have a user record, use `login!` with the proper password.
+
+```ruby
+user = Parse::User.login(username,password)
+user.session_token # session token from a Parse::Session
+user.session # Parse::Session tied to the token
+
+ # You can login user records
+user = Parse::User.first
+user.session_token # nil
+
+passwd = 'p_n7!-e8' # corresponding password
+user.login!(passwd) # true
+
+user.session_token # 'r:pnktnjyb996sj4p156gjtp4im'
+
+ # logout to delete the session
+user.logout
+```
+
+If you happen to already have a valid session token, you can use it to retrieve the corresponding Parse::User.
+
+```ruby
+# finds user with session token
+user = Parse::User.session(session_token)
+
+user.logout # deletes the corresponding session
+```
+
+#### Linking and Unlinking Users
+You can signup or login uses with third-party services like Facebook and Twitter as described in: [Linking and Unlinking Users](https://parseplatform.github.io/docs/rest/guide/#linking). To do this, you must first get the corresponding authentication data for the specific service, and then apply it to the user using the linking and unlinking methods. Each method returns true or false if the action was successful. For a listing of supported third-party authentication services, see [OAuth](https://github.com/ParsePlatform/parse-server/wiki/OAuth).
+
+```ruby
+
+user = Parse::User.first
+
+fb_auth = { ... } # Facebook auth data
+
+# Link this user's Facebook account with Parse
+user.link_auth_data! :facebook, fb_auth
+
+# Unlinks this user's Facebook account from Parse
+user.unlink_auth_data! :facebook
+```
+
+#### Request Password Reset
+You can reset a user's password using the `Parse::User.request_password_reset` method.
+
+```ruby
+user = Parse::User.first
+
+# pass a user object
+Parse::User.request_password_reset user
+# or email
+Parse::User.request_password_reset("user@example.com")
+```
+
 
 ## Modeling and Subclassing
 For the general case, your Parse classes should inherit from `Parse::Object`. `Parse::Object` utilizes features from `ActiveModel` to add several features to each instance of your subclass. These include `Dirty`, `Conversion`, `Callbacks`, `Naming` and `Serializers::JSON`.
@@ -524,19 +698,21 @@ end
 ### Defining Properties
 Properties are considered a literal-type of association. This means that a defined local property maps directly to a column name for that remote Parse class which contain the value. **All properties are implicitly formatted to map to a lower-first camelcase version in Parse (remote).** Therefore a local property defined as `like_count`, would be mapped to the remote column of `likeCount` automatically. The only special behavior to this rule is the `:id` property which maps to `objectId` in Parse. This implicit conversion mapping is the default behavior, but can be changed on a per-property basis. All Parse data types are supported and all Parse::Object subclasses already provide definitions for `:id` (objectId), `:created_at` (createdAt), `:updated_at` (updatedAt) and `:acl` (ACL) properties.
 
-- **:string** (_default_) - a generic string.
-- **:integer** - basic number.
+- **:string** (_default_) - a generic string. Can be used as an enum field, see [Enum](#enum).
+- **:integer** (alias **:int**) - basic number.
 - **:float** - a floating numeric value.
-- **:boolean** - true/false value. (_alias: `:bool`_).
-- **:date** - a Parse date type. Maps to `Parse::Date`.
-- **:array** - a collection of heterogeneous items. Maps to `Parse::CollectionProxy`.
-- **:file** - a Parse file type. Maps to `Parse::File`.
-- **:geopoint** - a GeoPoint type. Maps to `Parse::GeoPoint`.
-- **:bytes** - a Parse bytes data type managed as base64. Maps to `Parse::Bytes`.
-- **:object** - an object Hash data type.
+- **:boolean** (alias **:bool**) - true/false value. This will also generate a class scope helper. See [Query Scopes](#query-scopes).
+- **:date** - a Parse date type. See [Parse::Date](#parsedate).
+- **:array** - a heterogeneous list with dirty tracking. See [Parse::CollectionProxy](https://github.com/modernistik/parse-stack/blob/master/lib/parse/model/associations/collection_proxy.rb).
+- **:file** - a Parse file type. See [Parse::File](#parsefile).
+- **:geopoint** - a GeoPoint type. See [Parse::GeoPoint](#parsegeopoint).
+- **:bytes** - a Parse bytes data type managed as base64. See [Parse::Bytes](#parsebytes).
+- **:object** - an object "hash" data type. See [ActiveSupport::HashWithIndifferentAccess](http://apidock.com/rails/ActiveSupport/HashWithIndifferentAccess).
 
 For completeness, the `:id` and `:acl` data types are also defined in order to handle the Parse `objectId` field and the `ACL` object. Those are special and should not be used in your class (unless you know what you are doing). New data types can be implemented through the internal `typecast` interface. **TODO: discuss `typecast` interface in the future**
 
+In addition, `:boolean` data types create a special method that uses the `?` convention. As an example, if you have a property named `approved`, the normal getter `obj.approved` can return true, false or nil based on the value in Parse. However with the `obj.approved?` method, it will return true if it set to true, false for any other value.
+
 Using the example above, we can add the base properties to our classes.
 
 ```ruby
@@ -562,6 +738,9 @@ class Post < Parse::Object
   # a list using
   property :tags, :array
 
+  # string column as enummerated type. see :enum
+  property :status, enum: [:active, :archived]
+
   # Maps to "featuredImage" column representing a File.
   property :featured_image, :file
 
@@ -612,13 +791,13 @@ post.SEO # the alias method since 'field: "SEO"'
 #### Property Options
 These are the supported options when defining properties. Parse::Objects are backed by `ActiveModel`, which means you can add additional validations and features supported by that library.
 
-##### `:required => (true|false)`
-This option provides information to the property builder that it is a required property. The requirement is not strongly enforced for a save, which means even though the value for the property may not be present, saves and updates can be successfully performed. However, the setting `required` to true, it will set some ActiveModel validations on the property to be used when calling `valid?`. By default it will add a `validates_presence_of` for the property key. If the data type of the property is either `:integer` or `:float`, it will also add a `validates_numericality_of` validation. Default `false`.
+##### `:required`
+A boolean property. This option provides information to the property builder that it is a required property. The requirement is not strongly enforced for a save, which means even though the value for the property may not be present, saves and updates can be successfully performed. However, the setting `required` to true, it will set some ActiveModel validations on the property to be used when calling `valid?`. By default it will add a `validates_presence_of` for the property key. If the data type of the property is either `:integer` or `:float`, it will also add a `validates_numericality_of` validation. Default `false`.
 
-##### `:field => (string)`
+##### `:field`
 This option allows you to set the name of the remote column for the Parse table. Using this will explicitly set the remote property name to the value of this option. The value provided for this option will affect the name of the alias method that is generated when `alias` option is used. **By default, the name of the remote column is the lower-first camelcase version of the property name. As an example, for a property with key `:my_property_name`, the framework will implicitly assume that the remote column is `myPropertyName`.**
 
-##### `:default => (value|proc)`
+##### `:default`
 This option provides you to set a default value for a specific property when the getter accessor method is used and the internal value of the instance object's property is nil. It can either take a literal value or a Proc/lambda.
 
 ```ruby
@@ -630,11 +809,11 @@ class SomeClass < Parse::Object
 end
 ```
 
-##### `:alias => (true|false)`
-It is highly recommended that this is set to true, which is the default. This option allows for the generation of the additional accessors with the value of `:field`. By allowing two accessors methods, aliased to each other, allows for easier importing and automatic object instantiation based on Parse object JSON data into the Parse::Object subclass.
+##### `:alias`
+A boolean property. It is highly recommended that this is set to true, which is the default. This option allows for the generation of the additional accessors with the value of `:field`. By allowing two accessors methods, aliased to each other, allows for easier importing and automatic object instantiation based on Parse object JSON data into the Parse::Object subclass.
 
-##### `:symbolize => (true|false)`
-This option is only available for fields with data type of `:string`. This allows you to utilize the values for this property as symbols instead of the literal strings, which is Parse's storage format. This feature is useful if a particular property represents a set of enumerable states described in string form. As an example, if you have a `Post` object which has a set of publish states stored in Parse as "draft","scheduled", and "published" - we can use ruby symbols to make our code easier.
+##### `:symbolize`
+A boolean property. This option is only available for fields with data type of `:string`. This allows you to utilize the values for this property as symbols instead of the literal strings, which is Parse's storage format. This feature is useful if a particular property represents a set of enumerable states described in string form. As an example, if you have a `Post` object which has a set of publish states stored in Parse as "draft","scheduled", and "published" - we can use ruby symbols to make our code easier.
 
 ```ruby
 class Post < Parse::Object
@@ -650,14 +829,78 @@ if post.state == :draft
 end
 ```
 
-##### Overriding Property Accessors
-When a `property` is defined, special accessors are created for it. It is not recommended that you override the generated accessors for the properties you have defined.
+##### `:enum`
+The enum option allows you to define an array of possible values that the particular `:string` property should hold. This feature has similarities in the methods and accessors generated for you as described in [ActiveRecord::Enum](http://edgeapi.rubyonrails.org/classes/ActiveRecord/Enum.html). Using the example in that documentation:
+
+```ruby
+class Conversation < Parse::Object
+  property :status, enum: [ :active, :archived ]
+end
+
+Conversation.statuses # => [ :active, :archived ]
+
+# named scopes
+Conversation.active # where status: :active
+Conversation.archived(limit: 10) # where status: :archived, limit 10
+
+conversation.active! # sets status to active!
+conversation.active? # => true
+conversation.status  # => :active
+
+conversation.archived!
+conversation.archived? # => true
+conversation.status    # => :archived
+
+# equivalent
+conversation.status = "archived"
+conversation.status = :archived
+
+# allowed by the setter
+conversation.status = :banana
+conversation.status_valid? # => false
+
+```
+
+Similar to [ActiveRecord::Enum](http://edgeapi.rubyonrails.org/classes/ActiveRecord/Enum.html), you can use the `:_prefix` or `:_suffix` options when you need to define multiple enums with same values. If the passed value is true, the methods are prefixed/suffixed with the name of the enum. It is also possible to supply a custom value:
+
+```ruby
+class Conversation < Parse::Object
+  property :status, enum: [:active, :archived], _suffix: true
+  property :comments_status, enum: [:active, :inactive], _prefix: :comments
+  # combined
+  property :discussion, enum: [:casual, :business], _prefix: :talk, _suffix: true
+end
+
+Conversation.statuses # => [:active, :archived]
+Conversation.comments # => [:active, :inactive]
+Conversation.talks # => [:casual, :business]
+
+# affects scopes names
+Conversation.archived_status
+Conversation.comments_inactive
+Conversation.business_talk
+
+conversation.active_status!
+conversation.archived_status? # => false
+
+conversation.status = :banana
+conversation.valid_status? # => false
+
+conversation.comments_inactive!
+conversation.comments_active? # => false
+
+conversation.casual_talk!
+conversation.business_talk? # => false
+```
+
+##### `:scope`
+A boolean property. For some data types like `:boolean` and enums, some [query scopes](#query-scopes) are generated to more easily query data. To prevent generating these scopes for a particular property, set this value to `false`.
 
 ### Associations
 Parse supports a three main types of relational associations. One type of relation is the `One-to-One` association. This is implemented through a specific column in Parse with a Pointer data type. This pointer column, contains a local value that refers to a different record in a separate Parse table. This association is implemented using the `:belongs_to` feature. The second association is of `One-to-Many`. This is implemented is in Parse as a Array type column that contains a list of of Parse pointer objects. It is recommended by Parse that this array does not exceed 100 items for performance reasons. This feature is implemented using the `:has_many` operation with the plural name of the local Parse class. The last association type is a Parse Relation. These can be used to implement a large `Many-to-Many` association without requiring an explicit intermediary Parse table or class. This feature is also implemented using the `:has_many` method but passing the option of `:relation`.
 
 #### Belongs To
-Utilizing the `belongs_to` method in defining a property in a Parse::Object subclass sets up an association between the local table and a foreign table. Specifying the `belongs_to` in the class, tells the framework that the Parse table contains a local column in its schema that has a reference to a record in a foreign table. The argument to `belongs_to` should be the singularized version of the foreign Parse::Object class. you should specify the foreign table as the snake_case singularized version of the foreign table class. It is important to note that the reverse relationship is not generated automatically.
+This association creates a one-to-one association with another Parse model. This association says that this class contains a foreign pointer column which references a different class. Utilizing the `belongs_to` method in defining a property in a Parse::Object subclass sets up an association between the local table and a foreign table. Specifying the `belongs_to` in the class, tells the framework that the Parse table contains a local column in its schema that has a reference to a record in a foreign table. The argument to `belongs_to` should be the singularized version of the foreign Parse::Object class. you should specify the foreign table as the snake_case singularized version of the foreign table class. It is important to note that the reverse relationship is not generated automatically.
 
 ```ruby
 class Author < Parse::Object
@@ -683,12 +926,12 @@ post.save
 ```
 
 ##### Options
-You can override some of the default functionality when creating both `belongs_to` and `has_many` associations.
+You can override some of the default functionality when creating both `belongs_to`, `has_one` and `has_many` associations.
 
-###### `:required => (true|false)`
-Setting the requirement, automatically creates an ActiveModel validation of `validates_presence_of` for the association. This will not prevent the save, but affects the validation check when `valid?` is called on an instance. Default is false.
+###### `:required`
+A boolean property. Setting the requirement, automatically creates an ActiveModel validation of `validates_presence_of` for the association. This will not prevent the save, but affects the validation check when `valid?` is called on an instance. Default is false.
 
-###### `:as => (string)`
+###### `:as`
 This option allows you to override the foreign Parse class that this association refers while allowing you to have a different accessor name. As an example, you may have a class `Band` which has a `manager` who is of type `Parse::User` and a set of band members, represented by the class `Artist`. You can override the default casting class as follows:
 
 ```ruby
@@ -708,64 +951,226 @@ band.lead_singer # Artist object
 band.drummer # Artist object
 ```
 
-###### `:field => (string)`
+###### `:field`
 This option allows you to set the name of the remote Parse column for this property. Using this will explicitly set the remote property name to the value of this option. The value provided for this option will affect the name of the alias method that is generated when `alias` option is used. **By default, the name of the remote column is the lower-first camel case version of the property name. As an example, for a property with key `:my_property_name`, the framework will implicitly assume that the remote column is `myPropertyName`.**
 
-#### Has Many (Array or Relation)
-Parse has two ways of implementing a `has_many` association. The first type is where you can designate a column to be of Array type that contains a list of Parse pointers. It is recommended that this is used for associations where the quantity is less than 100 in order to maintain query and fetch performance. The second implementation is through a Parse Relation. This is done by passing the option `:through => :relation` to the `has_many` method. Designating a column as a Parse relation to another class type, will create a one-way intermediate "join" table between the local table class and the foreign one. One important distinction of this compared to other types of data stores (ex. PostgresSQL) is that:
+#### Has One
+The `has_one` creates a one-to-one association with another Parse class. This association says that the other class in the association contains a foreign pointer column which references instances of this class. If your model contains a column that is a Parse pointer to another class, you should use `belongs_to` for that association instead.
 
-1. The inverse relationship association is not available automatically. Therefore, having a column of `artists` in a `Band` class that relates to members of the band (as `Artist` class), does not automatically make a set of `Band` records available to `Artist` records for which they have been related. If you need to maintain both the inverse relationship between a foreign class to its associations, you will need to manually manage that.
-2. Querying the relation is actually performed against the implicit join table, not the local one.
-3. Applying query constraints for a set of records within a relation is performed against the foreign table class, not the class having the relational column.
+Defining a `has_one` property generates a helper query method to fetch a particular record from a foreign class. This is useful for setting up the inverse relationship accessors of a `belongs_to`. In the case of the `has_one` relationship, the `:field` option represents the name of the column of the foreign class where the Parse pointer is stored. By default, the lower-first camel case version of the Parse class name is used.
 
-The Parse documentation provides more details on associations, see [Parse Relations Guide](https://parse.com/docs/ios/guide#relations). The good news is that the framework will handle the work for (2) and (3) automatically.
+In the example below, a `Band` has a local column named `manager` which has a pointer to a `Parse::User` record. This setups up the accessor for `Band` objects to access the band's manager.
 
-To define a `has_many` association, provide the name of the foreign relation class in plural form. The framework will use the camelcase singular form of the property name as being the name of the foreign table class.
+```ruby
+# every band has a manager
+class Band < Parse::Object
+	belongs_to :manager, as: :user
+end
+
+band = Band.first id: '12345'
+# the user represented by this manager
+user = band.manger
+
+```
+
+Since we know there is a column named `manager` in the `Band` class that points to a single `Parse::User`, you can setup the inverse association read accessor in the `Parse::User` class. Note, that to change the association, you need to modify the `manager` property on the band instance since it contains the `belongs_to` property.
 
 ```ruby
+# every user manages a band
+class Parse::User
+  # inverse relationship to `Band.belongs_to :manager`
+  has_one :band, field: :manager
+end
+
+user = Parse::User.first
+# use the generated has_one accessor `band`.
+user.band # similar to query: Band.first(:manager => user)
+
+```
+
+You may optionally use `has_one` with scopes, in order to fine tune the query result. Using the example above, you can customize the query with a scope that only fetches the association if the band is approved. If the association cannot be fetched, `nil` is returned.
+
+```ruby
+# adding to previous example
+class Band < Parse::Object
+  property :approved, :boolean
+  property :approved_date, :date
+end
+
+# every user manages a band
+class Parse::User
+  has_one :recently_approved, ->{ where(order: :approved_date.desc) }, field: :manager, as: :band
+  has_one :band_by_status, ->(status) { where(approved: status) },  field: :manager, as: :band
+end
+
+# gets the band most recently approved
+user.recently_approved
+# equivalent: Band.first(manager: user, order: :approved_date.desc)
+
+# fetch the managed band that is not approved
+user.band_by_status(false)
+# equivalent: Band.first(manager: user, approved: false)
+
+```
+
+#### Has Many
+Parse has many ways to implement one-to-many and many-to-many associations: `Array`, `Parse Relation` or through a `Query`. How you decide to implement your associations, will affect how `has_many` works in Parse-Stack. Parse natively supports one-to-many and many-to-many relationships using `Array` and `Relations`, as described in [Relational Data](https://parseplatform.github.io/docs/js/guide/#relational-data). Both of these methods require you define a specific column type in your Parse table that will be used to store information about the association.
+
+In addition to `Array` and `Relation`, Parse-Stack also implements the standard `has_many` behavior prevalent in other frameworks through a query where the associated class contains a foreign pointer to the local class, usually the inverse of a `belongs_to`. This requires that the associated class
+
+##### Query
+In this implementation, a `has_many` association for a Parse class requires that another Parse class will have a foreign pointer that refers to instances of this class. This is the standard way that `has_many` relationships work in most databases systems. This is usually the case when you have a class that has a `belongs_to` relationship to instances of the local class.
+
+In the example below, many songs belong to a specific artist. We set this association by setting `:belongs_to` relationship from `Song` to `Artist`. Knowing there is a column in `Song` that points to instances of an `Artist`, we can setup a `has_many` association to `Song` instances in the `Artist` class. Doing so will generate a helper query method on the `Artist` instance objects.
+
+```ruby
+class Song < Parse::Object
+  property :released, :date
+  # this class will have a pointer column to an Artist
+  belongs_to :artist
+end
 
 class Artist < Parse::Object
+  has_many :songs
 end
 
-class Fan < Parse::Object
-	property :location, :geopoint
+artist = Artist.first
+
+artist.songs # => [all songs belonging to artist]
+# equivalent: Song.all(artist: artist)
+
+# filter also by release date
+artist.songs(:released.after => 1.year.ago)
+# equivalent: Song.all(artist: artist, :released.after => 1.year.ago)
+
+```
+
+In order to modify the associated objects (ex. `songs`), you must modify their corresponding `belongs_to` field (in this case `song.artist`), to another record and save it.
+
+Options for `has_many` using this approach are `:as` and `:field`. The `:as` option behaves similarly to the `:belongs_to` counterpart. The `:field` option can be used to override the derived column name located in the foreign class. The default value for `:field` is the columnized version of the Parse subclass `parse_class` method.
+
+```ruby
+class Parse::User
+  # since the foreign column name is :agent
+  has_many :artists, field: :agent
+end
+
+class Artist < Parse::Object
+  belongs_to :manager, as: :user, field: :agent
+end
+
+artist.manager # => Parse::User object
+
+user.artists # => [artists where :agent column is user]
+```
+
+When using this approach, you may also employ the use of scopes to filter the particular data from the `has_many` association.
+
+```ruby
+class Artist
+  has_many :songs, ->(timeframe) { where(:created_at.after => timeframe) }
+end
+
+artist.songs(6.months.ago)
+# => [artist's songs created in the last 6 months]
+
+```
+
+You may also call property methods in your scopes related to the local class. You also have access to the instance object for the local class through a special `:i` method in the scope.
+
+```ruby
+class Concert
+  property :city
+  belongs_to :artist
+end
+
+class Artist
+  property :hometown
+  has_many :local_concerts, -> { where(:city => hometown) }, as: :concerts
+end
+
+# assume
+artist.hometown = "San Diego"
+
+# artist's concerts in their hometown of 'San Diego'
+artist.local_concerts
+# equivalent: Concert.all(artist: artist, city: artist.hometown)
+
+```
+
+##### Array
+In this implementation, you can designate a column to be of `Array` type that contains a list of Parse pointers. Parse-Stack supports this by passing the option `through: :array` to the `has_many` method. If you use this approach, it is recommended that this is used for associations where the quantity is less than 100 in order to maintain query and fetch performance. You would be in charge of maintaining the array with the proper list of Parse pointers that are associated to the object. Parse-Stack does help by wrapping the array in a [Parse::PointerCollectionProxy](https://github.com/modernistik/parse-stack/blob/master/lib/parse/model/associations/pointer_collection_proxy.rb) which provides dirty tracking.
+
+```ruby
+class Artist < Parse::Object
 end
 
 class Band < Parse::Object
-  property :category, :integer, default: 1
-	# assume any band as < 100 members
-	has_many :artists # assumes `through: :array`
-	# bands can have millions of fans (Parse::User objects),
-  # we use relations instead
-	has_many :fans, as: :user, through: :relation 
+	has_many :artists, through: :array
 end
 
- # Find all bands which have a category in this array.
-bands = Band.all( :category.in => [1,3,5,7,9] )
+artist = Artist.first
+
+# find all bands that contain this artist
+bands = Band.all( :artists.in => [artist.pointer] )
 
- # Find all bands which have Joe as an artist.
-banjoe = Artist.first name: "Joe Banjoe"
-bands = Band.all( :artists.in => [banjoe.pointer] )
 band = bands.first
+band.artists # => [array of Artist pointers]
+
+# remove artists
+band.artists.remove artist
+
+# add artist
+band.artists.add artist
+
+# save changes
+band.save
+```
+
+##### Parse Relation
+Other than the use of arrays, Parse supports native one-to-many and many-to-many associations through what is referred to as a [Parse Relation](https://parseplatform.github.io/docs/js/guide/#many-to-many-relationships). This is implemented by defining a column to be of type `Relation` which refers to a foreign class. Parse-Stack supports this by passing the `through: :relation` option to the `has_many` method. Designating a column as a Parse relation to another class type, will create a one-way intermediate "join-list" between the local class and the foreign class. One important distinction of this compared to other types of data stores (ex. PostgresSQL) is that:
+
+1. The inverse relationship association is not available automatically. Therefore, having a column of `artists` in a `Band` class that relates to members of the band (as `Artist` class), does not automatically make a set of `Band` records available to `Artist` records for which they have been related. If you need to maintain both the inverse relationship between a foreign class to its associations, you will need to manually manage that by adding two Parse relation columns in each class, or by creating a separate class (ex. `ArtistBands`) that is used as a join table.
+2. Querying the relation is actually performed against the implicit join table, not the local one.
+3. Applying query constraints for a set of records within a relation is performed against the foreign table class, not the class having the relational column.
+
+The Parse documentation provides more details on associations, see [Parse Relations Guide](https://parse.com/docs/ios/guide#relations). Parse-Stack will handle the work for (2) and (3) automatically.
+
+In the example below, a `Band` can have thousands of `Fans`. We setup a `Relation<Fan>` column in the `Band` class that references the `Fan` class. Parse-Stack provides methods to manage the relationship under the [Parse::RelationCollectionProxy](https://github.com/modernistik/parse-stack/blob/master/lib/parse/model/associations/relation_collection_proxy.rb) class.
+
+```ruby
+
+class Fan < Parse::Object
+  # .. lots of properties ...
+	property :location, :geopoint
+end
+
+class Band < Parse::Object
+	has_many :fans, through: :relation 
+end
+
+band = Band.first
 
  # the number of fans in the relation
 band.fans.count
 
 # get the first object in relation
-fan = bands.fans.first
+fan = bands.fans.first # => Parse::User object
 
 # use `add` or `remove` to modify relations
-band.fans.add Parse::User.first
+band.fans.add user
+bands.fans.remove user
+
 # updates the relation as well as changes to `band`
 band.fans.save
 
- # Find 50 fans who are near San Diego, CA
+# Find 50 fans who are near San Diego, CA
 downtown = Parse::GeoPoint.new(32.82, -117.23)
-fans = band.fans.all(:location.near => downtown, :limit => 50)
+fans = band.fans.all :location.near => downtown
 
 ```
 
-You can perform atomic additions and removals of objects from `has_many` relations. Parse allows this by providing a specific atomic operation request. You can use the methods below to perform these types of atomic operations. __Note: The operation is performed directly on Parse server and not on your local object.__
+You can perform atomic additions and removals of objects from `has_many` relations. Parse allows this by providing a specific atomic operation request. You can use the methods below to perform these types of atomic operations. __Note: The operation is performed directly on Parse server and not on your instance object.__
 
 ```ruby
 
@@ -787,10 +1192,31 @@ band.op_destroy!("category") # { __op: :Delete }
 ```
 
 ##### Options
-Options for `has_many` are the same as the `belongs_to` counterpart with support for `:required`, `:as` and `:field`. It has this additional option of `:through` which helps specify whether it is an Array or Relation association type.
+Options for `has_many` are the same as the `belongs_to` counterpart with support for `:required`, `:as` and `:field`. It has these additional options.
+
+###### `:through`
+This sets the type of the `has_many` relation whose possible values are `:array`, `:relation` or `:query` (implicit default). If set to `:array`, it defines the column in Parse as being an array of Parse pointer objects and will be managed locally using a `Parse::PointerCollectionProxy`. If set to `:relation`, it defines a column of type Parse Relation with the foreign class and will be managed locally using a `Parse::RelationCollectionProxy`. If set to `:query`, no storage is required on the local class as the associated records will be fetched using a Parse query.
+
+###### `:scope_only`
+Setting this option to `true`, makes the association fetch based only on the scope provided and does not use the local instance object as a foreign pointer in the query. This allows for cases where another property of the local class, is needed to match the resulting records in the association.
 
-###### `:through => (:array|:relation)`
-This sets the type of the `has_many` relation. If `:relation` is set, it tells the framework that the column defined is of type Parse Relation. The default value is `:array`, which defines the column in Parse as being an array of Parse pointer objects.
+In the example below, the `Post` class does not have a `:belongs_to` association to `Author`, but using the author's name, we can find related posts.
+
+```ruby
+
+class Author < Parse::Object
+  property :name
+  has_many :posts, ->{ where :tags.in => name.downcase }, scope_only: true
+end
+
+class Post < Parse::Object
+  property :tags, :array
+end
+
+author.posts # => Posts where author's name is a tag
+# equivalent: Post.all( :tags.in => artist.name.downcase )
+
+```
 
 ## Creating, Saving and Deleting Records
 This section provides some of the basic methods when creating, updating and deleting objects from Parse. To illustrate the various methods available for saving Parse records, we use this example class:
@@ -1536,6 +1962,59 @@ query.or_where(:wins.lt => 5)
 results = query.results
 ```
 
+## Query Scopes
+This feature is a small subset of the [ActiveRecord named scopes](http://guides.rubyonrails.org/active_record_querying.html#scopes) feature. Scoping allows you to specify commonly-used queries which can be referenced as class method calls and are chainable with other scopes. You can use every `Parse::Query` method previously covered such as `where`, `includes` and `limit`.
+
+```ruby
+
+class Article < Parse::Object
+  property :published, :boolean
+  scope :published, -> { query(published: true) }
+end
+```
+
+This is the same as defining your own class method for the query.
+
+```ruby
+class Article < Parse::Object
+  def self.published
+    query(published: true)
+  end
+end
+```
+
+You can also chain scopes and pass parameters. In addition, boolean and enumerated properties have automatically generated scopes for you to use.
+
+```ruby
+
+class Article < Parse::Object
+  scope :published, -> { query(published: true) }
+
+  property :comment_count, :integer
+  property :category
+  property :approved, :boolean
+
+  scope :published_and_commented, -> { published.where :comment_count.gt => 0 }
+  scope :popular_topics, ->(name) { published_and_commented.where category: name }
+end
+
+# simple scope
+Article.published # => where published is true
+
+# chained scope
+Article.published_and_commented # published is true and comment_count > 0
+
+# scope with parameters
+Article.popular_topic("music") # => popular music articles
+# equivalent: where(published: true, :comment_count.gt => 0, category: name)
+
+# automatically generated scope
+Article.approved(category: "tour") # => where approved: true, category: 'tour'
+
+```
+
+If you would like to turn off automatic scope generation for property types, set the option `:scope` to false when declaring the property.
+
 ## Calling Cloud Code Functions
 You can call on your defined Cloud Code functions using the `call_function()` method. The result will be `nil` in case of errors or the value of the `result` field in the Parse response.
 
@@ -1562,8 +2041,8 @@ You can trigger background jobs that you have configured in your Parse applicati
  response.result unless response.error?
 ```
 
-## Model Callbacks
-All `Parse::Object` subclasses extend [`ActiveModel::Callbacks`](http://api.rubyonrails.org/classes/ActiveModel/Callbacks.html) for `#save` and `#destroy` operations. You can setup internal hooks for `before`, `during` and `after`. See
+## Active Model Callbacks
+All `Parse::Object` subclasses extend [`ActiveModel::Callbacks`](http://api.rubyonrails.org/classes/ActiveModel/Callbacks.html) for `#save` and `#destroy` operations. You can setup internal hooks for `before` and `after`.
 
 ```ruby
 
@@ -1575,6 +2054,10 @@ class Song < Parse::Object
 		acl.everyone(true, false) if new?
 	end
 
+  after_create do
+    puts "New object successfully saved."
+  end
+
 end
 
 song = Song.new name: "my title"
@@ -1584,6 +2067,8 @@ puts song.name # 'My Title'
 
 ```
 
+There are also a special `:create` callback. A `before_create` will be called whenever a unsaved object will be saved, and `after_create` will be called when a previously unsaved object successfully saved for the first time.
+
 ## Schema Upgrades and Migrations
 You may change your local Parse ruby classes by adding new properties. To easily propagate the changes to your Parse application (MongoDB), you can call `auto_upgrade!` on the class to perform an non-destructive additive schema change. This will create the new columns in Parse for the properties you have defined in your models. Parse Stack will calculate the changes and only modify the tables which need new columns to be added. *It will not destroy columns or data*
 
@@ -1646,7 +2131,7 @@ end
 # Parse::Webhooks.route :function, :myFunc, MyClass.method(:my_func)
 ```
 
-If you have registered this webhook (see instructions below), you should be able to test it out by running curl using the command below. For a more in-depth example, see [Parse-Server-Rails-Example](https://github.com/modernistik/parse-server-rails-example).
+If you have registered this webhook (see instructions below), you should be able to test it out by running curl using the command below.
 
 ```bash
 curl -X POST \
@@ -1816,8 +2301,8 @@ If you are already have setup a client that is being used by your defined models
   client = Song.client
 
   # you can also have multiple clients
-  client = Parse::Client.session #default client session
-  client = Parse::Client.session(:other_session)
+  client = Parse::Client.client #default client session
+  client = Parse::Client.client(:other_session)
 
 ```
 
@@ -1843,7 +2328,7 @@ same_user = Parse::User.first # cached result
 
 # you may clear the cache at any time
 # clear the cache for the default session
-Parse::Client.session.clear_cache!
+Parse::Client.client.clear_cache!
 
 # or through the client accessor of a model
 Song.client.clear_cache!