[Bps-public-commit] rt-extension-assets branch, assetsearchformat-example, created. 1.01_1-1-gdb4325a

[Kevin Falcone]

The branch, assetsearchformat-example has been created
        at  db4325ac91f6b9314c8ef6daf836876d48f74a16 (commit)

- Log -----------------------------------------------------------------
commit db4325ac91f6b9314c8ef6daf836876d48f74a16
Author: Kevin Falcone <falcone at bestpractical.com>
Date:   Tue Sep 30 12:01:32 2014 -0400

    Show a sample of the hashref syntax for AssetSearchFormat
    
    Even though we only have one Catalog out of the box, this helps admins
    who aren't perl programmers understand the format of multiple-catalog
    formats.

diff --git a/etc/Assets_Config.pm b/etc/Assets_Config.pm
index 3309d2f..d97b5a5 100644
--- a/etc/Assets_Config.pm
+++ b/etc/Assets_Config.pm
@@ -116,6 +116,15 @@ either a string, which will be used for all catalogs, or a hash
 reference, keyed by catalog's name/id.  If a hashref and neither name or
 id is found therein, falls back to the key ''.
 
+If you wish to use the multiple catalog format, your configuration would look
+something like:
+
+    Set($AssetSearchFormat, {
+        'General assets' => q[Format String for the General Assets Catalog],
+        8                => q[Format String for Catalog 8],
+        ''               => q[Format String for any catalogs not listed explicitly],
+    });
+
 =cut
 
 # loc('Related tickets')

-----------------------------------------------------------------------