Merge pull request #960 from plaes/doc-fixes

Various minor documentation fixes

doc/api/mod_actions.rst

 ``flask_admin.actions``
-===========================
+=======================
 
 .. automodule:: flask_admin.actions
 

doc/api/mod_base.rst

 ``flask_admin.base``
-========================
+====================
 
 .. automodule:: flask_admin.base
 

doc/api/mod_contrib_fileadmin.rst

 ``flask_admin.contrib.fileadmin``
-=====================================
+=================================
 
 .. automodule:: flask_admin.contrib.fileadmin
 

doc/api/mod_contrib_mongoengine.rst

 ``flask_admin.contrib.mongoengine``
-=======================================
+===================================
 
 MongoEngine model backend implementation.
 

doc/api/mod_contrib_mongoengine_fields.rst

 ``flask_admin.contrib.mongoengine.fields``
-==============================================
+==========================================
 
 .. automodule:: flask_admin.contrib.mongoengine.fields
 

doc/api/mod_contrib_peewee.rst

 ``flask_admin.contrib.peewee``
-==================================
+==============================
 
 Peewee model backend implementation.
 

doc/api/mod_contrib_pymongo.rst

 ``flask_admin.contrib.pymongo``
-===================================
+===============================
 
 PyMongo model backend implementation.
 

doc/api/mod_contrib_sqla.rst

 ``flask_admin.contrib.sqla``
-================================
+============================
 
 SQLAlchemy model backend implementation.
 

doc/api/mod_form.rst

 ``flask_admin.form``
-========================
+====================
 
 .. automodule:: flask_admin.form
 

doc/api/mod_form_upload.rst

 ``flask_admin.form.upload``
-===============================
+===========================
 
 .. automodule:: flask_admin.form.upload
 
@@ -10,7 +10,4 @@
 		:members: __init__
 
 	.. autoclass:: FileUploadInput
-		:members: __init__
-
 	.. autoclass:: ImageUploadInput
-		:members: __init__

doc/api/mod_helpers.rst

 ``flask_admin.helpers``
-===========================
+=======================
 
 .. automodule:: flask_admin.helpers
 

doc/api/mod_model.rst

 ``flask_admin.model``
-=========================
+=====================
 
 .. automodule:: flask_admin.model
 

doc/api/mod_model_template.rst

 ``flask_admin.model.template``
-==================================
+==============================
 
 .. automodule:: flask_admin.model.template
 

doc/api/mod_tools.rst

 ``flask_admin.tools``
-=========================
+=====================
 
 .. automodule:: flask_admin.tools
 

doc/introduction.rst

@@ -280,7 +280,7 @@ When your forms contain foreign keys, have those **related models loaded via aja
 
     form_ajax_refs = {
         'user': {
-            'fields': ['first_name', 'last_name', 'email']
+            'fields': ['first_name', 'last_name', 'email'],
             'page_size': 10
         }
     }
@@ -342,7 +342,7 @@ For this you could override only the view in question, and all the links to it w
     # Flask and Flask-SQLAlchemy initialization here
 
     class UserView(ModelView):
-    @expose('/new/', methods=('GET', 'POST'))
+        @expose('/new/', methods=('GET', 'POST'))
         def create_view(self):
         """
             Custom create view.
@@ -474,7 +474,7 @@ To generate the URL for a specific view, use *url_for* with a dot prefix::
 
     class MyView(BaseView):
         @expose('/')
-        def index(self)
+        def index(self):
             # Get URL for the test view method
             user_list_url = url_for('user.index_view')
             return self.render('index.html', user_list_url=user_list_url)
@@ -492,4 +492,4 @@ unique endpoint for each, and using that as the prefix. So, you could use::
 
 If your view endpoint was defined like::
 
-    admin.add_view(CustomView(name='Analytics', endpoint='analytics'))
\ No newline at end of file
+    admin.add_view(CustomView(name='Analytics', endpoint='analytics'))

flask_admin/contrib/sqla/view.py

@@ -96,19 +96,19 @@ class ModelView(BaseModelView):
 
         The following search rules apply:
 
-        - If you enter *ZZZ* in the UI search field, it will generate *ILIKE '%ZZZ%'*
+        - If you enter ``ZZZ`` in the UI search field, it will generate ``ILIKE '%ZZZ%'``
           statement against searchable columns.
 
         - If you enter multiple words, each word will be searched separately, but
           only rows that contain all words will be displayed. For example, searching
-          for 'abc def' will find all rows that contain 'abc' and 'def' in one or
+          for ``abc def`` will find all rows that contain ``abc`` and ``def`` in one or
           more columns.
 
-        - If you prefix your search term with ^, it will find all rows
-          that start with ^. So, if you entered *^ZZZ*, *ILIKE 'ZZZ%'* will be used.
+        - If you prefix your search term with ``^``, it will find all rows
+          that start with ``^``. So, if you entered ``^ZZZ`` then ``ILIKE 'ZZZ%'`` will be used.
 
-        - If you prefix your search term with =, it will perform an exact match.
-          For example, if you entered *=ZZZ*, the statement *ILIKE 'ZZZ'* will be used.
+        - If you prefix your search term with ``=``, it will perform an exact match.
+          For example, if you entered ``=ZZZ``, the statement ``ILIKE 'ZZZ'`` will be used.
     """
 
     column_filters = None
@@ -170,9 +170,9 @@ class ModelView(BaseModelView):
         giving SQLAlchemy a chance to manually cleanup any dependencies (many-to-many
         relationships, etc).
 
-        If set to `True`, will run a `DELETE` statement which is somewhat faster,
-        but may leave corrupted data if you forget to configure `DELETE
-        CASCADE` for your model.
+        If set to `True`, will run a ``DELETE`` statement which is somewhat faster,
+        but may leave corrupted data if you forget to configure ``DELETE
+        CASCADE`` for your model.
     """
 
     inline_models = None
@@ -201,12 +201,12 @@ class ModelView(BaseModelView):
 
         You can customize the generated field name by:
 
-        1. Using the `form_name` property as a key to the options dictionary:
+        1. Using the `form_name` property as a key to the options dictionary::
 
             class MyModelView(ModelView):
                 inline_models = ((Post, dict(form_label='Hello')))
 
-        2. Using forward relation name and `column_labels` property:
+        2. Using forward relation name and `column_labels` property::
 
             class Model1(Base):
                 pass
@@ -231,7 +231,7 @@ class ModelView(BaseModelView):
             class MyModelView(BaseModelView):
                 form_choices = {'my_form_field': [
                     ('db_value', 'display_value'),
-                ]
+                ]}
     """
 
     form_optional_types = (Boolean,)
@@ -732,10 +732,10 @@ class ModelView(BaseModelView):
         """
             Return a the count query for the model type
 
-            A query(self.model).count() approach produces an excessive
-            subquery, so query(func.count('*')) should be used instead.
+            A ``query(self.model).count()`` approach produces an excessive
+            subquery, so ``query(func.count('*'))`` should be used instead.
 
-            See #45a2723 commit message for details.
+            See commit ``#45a2723`` for details.
         """
         return self.session.query(func.count('*')).select_from(self.model)
 

flask_admin/model/base.py

@@ -513,7 +513,7 @@ class BaseModelView(BaseView, ActionsMixin):
             class MyModelView(BaseModelView):
                 form_ajax_refs = {
                     'user': {
-                        'fields': ('first_name', 'last_name', 'email')
+                        'fields': ('first_name', 'last_name', 'email'),
                         'page_size': 10
                     }
                 }