From ce6469a8eaaaaed02ee0ded003a26963ba4f720e Mon Sep 17 00:00:00 2001 From: Nick Reilingh Date: Fri, 10 Feb 2023 00:20:46 -0500 Subject: [PATCH] RT_Config.pm.in: PriorityAsString documentation The code example's ordering did not match the prose. Also, `=>` being equivalent to `,` is not commonly known to someone who may be trying to configure this setting through the 5.0 web configuration interface which accepts JSON, so using `,` in the `ArrayRef` variant is more helpful. --- etc/RT_Config.pm.in | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/etc/RT_Config.pm.in b/etc/RT_Config.pm.in index 8a8e48d28fb..84ebbe3dce2 100644 --- a/etc/RT_Config.pm.in +++ b/etc/RT_Config.pm.in @@ -2859,25 +2859,25 @@ giving a unique number to each. Set(%PriorityAsString, Default => { Low => 0, Medium => 50, High => 100 }, - General => [ Medium => 50, Low => 0, High => 80, 'On Fire' => 100], + General => [ Medium, 50, Low, 0, High, 80, 'On Fire', 100], Support => 0, ); The key is queue name or "Default", which is the fallback for unspecified -queues. Values can be an ArrayRef, HashRef, or C<0>. +queues. Values can be an HashRef, ArrayRef, or C<0>. =over -=item ArrayRef - -This is the ordered String => Number map list. Priority options will be -rendered in the order they are listed in the list. - =item HashRef This is the unordered String => Number map list. Priority options will be rendered in numerical ascending order. +=item ArrayRef + +This is the ordered String => Number map list. Priority options will be +rendered in the order they are listed in the list. + =item C<0> Priority is rendered as a number.