From eefcb79bfb4ce2bd0236fc4bb5d960a6df9f3cc4 Mon Sep 17 00:00:00 2001 From: Mark Michelson Date: Wed, 2 Apr 2014 18:57:29 +0000 Subject: Prevent duplicate sorcery wizards from being applied to sorcery object types. This commit contains several changes to sorcery: 1) Application of sorcery configuration based on module name is automatically performed when sorcery is opened for a module. 2) Sorcery will not attempt to apply the same wizard to an object type more than once. 3) Sorcery gives more exact results when attempting to apply a wizard, whether as the default or based on configuration. Sorcery unit tests still pass for me after making these changes. Review: https://reviewboard.asterisk.org/r/3326 ........ Merged revisions 411159 from http://svn.asterisk.org/svn/asterisk/branches/12 git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@411656 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- configs/sorcery.conf.sample | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'configs') diff --git a/configs/sorcery.conf.sample b/configs/sorcery.conf.sample index ee1300360..7406214fb 100644 --- a/configs/sorcery.conf.sample +++ b/configs/sorcery.conf.sample @@ -41,7 +41,7 @@ ; ; The following object mappings are used by the unit test to test certain functionality of sorcery. ; -[test_sorcery] +[test_sorcery_section] test=memory [test_sorcery_cache] -- cgit v1.2.3