[grilo] doc: use semicolon in ignored-parameters
- From: Juan A. Suarez Romero <jasuarez src gnome org>
- To: commits-list gnome org
- Cc: 
- Subject: [grilo] doc: use semicolon in ignored-parameters
- Date: Fri, 23 Aug 2013 14:56:32 +0000 (UTC)
commit 8bcf9eafafebe18e008ebe7f90ed27764d8331c8
Author: Juan A. Suarez Romero <jasuarez igalia com>
Date:   Fri Aug 23 14:53:55 2013 +0000
    doc: use semicolon in ignored-parameters
    
    ignored-parameters is a list of keys to be ignored when dealing with mockup
    network content.
    
    While in theory we can use either a colon or semicolon to separate the
    parameters, according to GKeyFile documentation, using colon doesn't work very
    well.
    
    So let's suggest to use semicolon.
 doc/grilo/plugins-testing.xml |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)
---
diff --git a/doc/grilo/plugins-testing.xml b/doc/grilo/plugins-testing.xml
index 151c1fc..c30bec6 100644
--- a/doc/grilo/plugins-testing.xml
+++ b/doc/grilo/plugins-testing.xml
@@ -116,7 +116,7 @@ $ export GRL_DEBUG="registry:*"
     <programlisting>
 [default]
 version = 1
-ignored-parameters = field1[,field2[,...]] or "*"
+ignored-parameters = field1[;field2[;...]] or "*"
 
 [http://www.example.com]
 data = content/of/response.txt
@@ -142,14 +142,14 @@ timeout = 500
           </listitem>
 
           <listitem>
-            <varname>ignored-parameters</varname> is a comma separated list of
+            <varname>ignored-parameters</varname> is a semicolon separated list of
             query parameter names that can be used to map URLs to sections
             without paying attention to query parameters listed here.
             By setting a value of "api_key" a request for
             <code>http://www.example.com?q=test+query&api_key=dummy</code>
             will be answered with the mock data for
             <code>http://www.example.com?q=test+query</code>.
-            Setting "api_key,q" or "*" will result in mock answer for
+            Setting "api_key;q" or "*" will result in mock answer for
             <code>http://www.example.com</code>.
           </listitem>
         </itemizedlist>
[
Date Prev][
Date Next]   [
Thread Prev][
Thread Next]   
[
Thread Index]
[
Date Index]
[
Author Index]