Bumping version and doc fixes

tjpnz · Jan 2, 2018 · d82cc0d · d82cc0d
1 parent c482f4a
commit d82cc0d
Show file tree

Hide file tree

Showing 4 changed files with 5 additions and 4 deletions.
diff --git a/README.md b/README.md
@@ -1,6 +1,7 @@
 # Flask-Validates
 
 [![Build Status](https://travis-ci.org/tjpnz/flask-validates.svg?branch=master)](https://travis-ci.org/tjpnz/flask-validates)
+[![Documentation Status](https://readthedocs.org/projects/flask-validates/badge/)](http://flask-validates.readthedocs.org/en/latest/)
 
 Painless form validation ([WTForms](https://github.com/wtforms/wtforms) or [Flask-WTF](https://github.com/lepture/flask-wtf)) using view decorators.
 

diff --git a/docs/conf.py b/docs/conf.py
@@ -15,8 +15,8 @@
 project = "Flask-Validates"
 copyright = "2018, Thomas Prebble"
 author = "Thomas Prebble"
-version = "0.1.0"
-release = "0.1.0"
+version = "0.2.0"
+release = "0.2.0"
 
 
 # -- Options for HTML output ----------------------------------------------

diff --git a/docs/index.rst b/docs/index.rst
@@ -15,7 +15,7 @@ Using pip:
 Usage
 -----
 
-Flask-Validates binds forms to views using the :func:`~flask_validates.validates` decorator, depending on how you use it Flask-Validates can eliminate the need entirely to create explicit form classes. When a view is invoked :func:`~flask_validates.validates` creates a form behind the scenes based on the fields you provide which is then exposed to the view via :data:`flask_validates.current_form` which works in a similar manner to Flask's :data:`flask.current_app`.
+Flask-Validates binds forms to views using the :func:`~flask_validates.validates` decorator, depending on how you use it Flask-Validates can eliminate the need entirely to create explicit form classes. When a view is invoked :func:`~flask_validates.validates` creates a form behind the scenes based on the fields you provide which is then exposed to the view via :data:`~flask_validates.current_form` which works in a similar manner to Flask's :data:`flask.current_app`.
 
 Alongside creating forms :func:`~flask_validates.validates` also sets the appropriate HTTP 400 response code if form validation fails.
 

diff --git a/setup.py b/setup.py
@@ -3,7 +3,7 @@
 
 setup(
     name="Flask-Validates",
-    version="0.1.0",
+    version="0.2.0",
     url="https://github.com/tjpnz/flask-validates",
     license="MIT",
     author="Thomas Prebble",
-Original file line number
+Diff line change
@@ Expand Up / @@ -15,7 +15,7 @@ Using pip: @@
     Usage
     -----
-    Flask-Validates binds forms to views using the :func:`~flask_validates.validates` decorator, depending on how you use it Flask-Validates can eliminate the need entirely to create explicit form classes. When a view is invoked :func:`~flask_validates.validates` creates a form behind the scenes based on the fields you provide which is then exposed to the view via :data:`flask_validates.current_form` which works in a similar manner to Flask's :data:`flask.current_app`.
+    Flask-Validates binds forms to views using the :func:`~flask_validates.validates` decorator, depending on how you use it Flask-Validates can eliminate the need entirely to create explicit form classes. When a view is invoked :func:`~flask_validates.validates` creates a form behind the scenes based on the fields you provide which is then exposed to the view via :data:`~flask_validates.current_form` which works in a similar manner to Flask's :data:`flask.current_app`.
     Alongside creating forms :func:`~flask_validates.validates` also sets the appropriate HTTP 400 response code if form validation fails.
@@ Expand Down @@