Add missing bundle to doc and remove redundant whitespace

bundles/index.rst

@@ -12,6 +12,7 @@
 * `UIBundle`_
 * `UserBundle`_
 * `VersioningBundle`_
+* `WebServiceBundle`_
 
 .. _CatalogBundle: https://github.com/akeneo/pim-community-dev/tree/master/src/Pim/Bundle/CatalogBundle
 .. _DashboardBundle: https://github.com/akeneo/pim-community-dev/tree/master/src/Pim/Bundle/DashboardBundle
@@ -27,3 +28,4 @@
 .. _UIBundle: https://github.com/akeneo/pim-community-dev/tree/master/src/Pim/Bundle/UIBundle
 .. _UserBundle: https://github.com/akeneo/pim-community-dev/tree/master/src/Pim/Bundle/UserBundle
 .. _VersioningBundle: https://github.com/akeneo/pim-community-dev/tree/master/src/Pim/Bundle/VersioningBundle
+.. _WebServiceBundle: https://github.com/akeneo/pim-community-dev/tree/master/src/Pim/Bundle/WebServiceBundle

contributing/contributing.rst

@@ -65,4 +65,3 @@ Submitting a Feature Request
 
 * you can propose any feature there http://www.akeneo.com/forum/feature-request/
 * after discussion this feature could be planned in our roadmap
-

contributing/map.rst.inc

@@ -10,4 +10,3 @@
 .. _Coding standard: http://symfony.com/doc/current/contributing/code/standards.html
 .. _Code conventions: http://symfony.com/doc/current/contributing/code/conventions.html
 .. _License agreement: http://www.akeneo.com/contributor-license-agreement/
-

cookbook/custom_entity/importing_custom_entities.rst

@@ -11,7 +11,7 @@ To ensure your entity is imported correctly, the first step is to implement the
 .. literalinclude:: ../../src/Pim/Bundle/IcecatDemoBundle/Entity/Vendor.php
    :language: php
    :lines: 1-5,8,17-18,183-
-   :linenos: 
+   :linenos:
 
 
 Your entity repository should implement the ``Pim\Bundle\CatalogBundle\Entity\Repository\ReferableEntityRepositoryInterface`` interface,
@@ -21,7 +21,7 @@ or be a subclass of ``Pim\Bundle\CatalogBundle\Entity\Repository\ReferableEntity
    :language: yaml
    :prepend: # /src/Pim/Bundle/IcecatDemoBundle/Resources/config/doctrine/Vendor.orm.yml
    :lines: 1,4
-   :linenos: 
+   :linenos:
 
 Attribute value importation
 ---------------------------
@@ -34,7 +34,7 @@ and the importation will be done automatically.
 If you have indirect associations, or if you cannot implement the interfaces in your entity and your repository,
 you will have to create a specific property transformer for your attribute type. (see :doc:`../import_export/customize-import-behavior` for more explanations)
 
-To use of your property transformer, you will have to configure a guesser service similar to the one used by 
+To use of your property transformer, you will have to configure a guesser service similar to the one used by
 price collection attributes :
 
 .. code-block:: yaml
@@ -62,7 +62,7 @@ interface, creating the processor is done by simply configuring a new service in
 .. literalinclude:: ../../src/Pim/Bundle/IcecatDemoBundle/Resources/config/processors.yml
    :language: yaml
    :prepend: # /src/Pim/Bundle/IcecatDemoBundle/Resources/config/processors.yml
-   :linenos: 
+   :linenos:
 
 Configure fixtures
 ------------------
@@ -72,7 +72,7 @@ The order and the processor for your fixtures is given in the ``fixtures.yml`` c
 .. literalinclude:: ../../src/Pim/Bundle/IcecatDemoBundle/Resources/config/fixtures.yml
    :language: yaml
    :prepend: # /src/Pim/Bundle/IcecatDemoBundle/Resources/config/fixtures.yml
-   :linenos: 
+   :linenos:
 
 You can now add a ``vendors.csv`` or a ``vendors.yml`` file in your fixtures folder, it will be
 loaded with other fixtures. (see :doc:`../setup_data/customize_installer`)

cookbook/import_export/customize-import-behavior.rst

@@ -15,7 +15,7 @@ For example, to skip all columns starting by a ``#``, the following guesser coul
 
 .. literalinclude:: ../../src/Acme/Bundle/DemoConnectorBundle/Transformer/Guesser/CommentGuesser.php
    :language: php
-   :linenos: 
+   :linenos:
 
 The way the guesser works is simple :
 
@@ -27,7 +27,7 @@ The guesser must be included in the following way in the DIC :
 .. literalinclude:: ../../src/Acme/Bundle/DemoConnectorBundle/Resources/config/guessers.yml
    :language: yaml
    :prepend: # /src/Acme/Bundle/DemoConnectorBundle/Resources/config/guessers.yml
-   :linenos: 
+   :linenos:
 
 As you can see, the transformer returned by the guesser will be the ``pim_import_export.transformer.property.skip``
 transformer.
@@ -39,7 +39,7 @@ In the following example, we create a transformer which prepends a string to a s
 
 .. literalinclude:: ../../src/Acme/Bundle/DemoConnectorBundle/Transformer/Property/PrependTransformer.php
    :language: php
-   :linenos: 
+   :linenos:
 
 This transformer prepends a string comming to the value, to make it work, you should therefore add
 a custom guesser which returns the value to be prepended in the options.
@@ -49,4 +49,4 @@ To add the transformer to the DIC, proceed in the following way:
 .. literalinclude:: ../../src/Acme/Bundle/DemoConnectorBundle/Resources/config/transformers.yml
    :language: yaml
    :prepend: # /src/Acme/Bundle/DemoConnectorBundle/Resources/config/transformers.yml
-   :linenos: 
+   :linenos:

cookbook/validation/customize_validation.rst

@@ -11,7 +11,7 @@ For example, to allow spaces in option codes, create the following file:
 .. literalinclude:: ../../src/Acme/Bundle/CatalogBundle/Resources/config/validation/attribute.yml
    :language: yaml
    :emphasize-lines: 171-
-   :linenos: 
+   :linenos:
 
 As you can see all the validation rules must be copied back in your file.
 

quickstart/map.rst.inc

@@ -1,4 +1,3 @@
 * `Install community edition`_
 
 .. _Install community edition: https://github.com/akeneo/pim-community-standard/blob/master/README.md
-

references/basic/technical_entities.rst

@@ -60,4 +60,3 @@ Note that, except the identifier attribute (usually the SKU), there is no requir
 An attribute is expected for a channel, for instance, description can be required for e-commerce but not for mobile.
 
 The product completeness is calculated for each channel and locale combination.
-

references/map.rst.inc

@@ -1,3 +1,2 @@
 * Basic
     * :doc:`/references/basic/technical_entities`
-